Storage availability using cryptographic splitting

ABSTRACT

Methods and systems for maintaining data connectivity in a secure data storage network are disclosed. In one aspect, a method includes assigning a volume to a primary secure storage appliance located in a secure data storage network the primary secure storage appliance selected from among a plurality of secure storage appliances located in the secure data storage network, the volume presented as a virtual disk to a client device and mapped to physical storage at each of a plurality of storage systems. The method further includes detecting at one of the plurality of secure storage appliances a failure of the primary secure storage appliance. The method also includes, upon detecting the failure of the primary secure storage appliance, reassigning the volume to a second secure storage appliance from among the plurality of secure storage appliances, thereby rendering the second secure storage appliance a new primary secure storage appliance.

RELATED APPLICATIONS

The present disclosure claims the benefit of commonly assigned U.S.patent application Ser. No. 12/272,012, entitled “BLOCK LEVEL DATASTORAGE SECURITY SYSTEM”, filed 17 Nov. 2008. The present disclosurealso claims the benefit of commonly assigned U.S. patent applicationSer. No. 12/336,558, entitled “DATA RECOVERY USING ERROR STRIPIDENTIFIERS”, filed 17 Dec. 2008.

The present disclosure is related to commonly assigned, and concurrentlyfiled, U.S. patent application Ser. No. 12/336,559 entitled “STORAGESECURITY USING CRYPTOGRAPHIC SPLITTING”, filed 17 Dec. 2008. The presentdisclosure is also related to commonly assigned, U.S. patent applicationSer. No. 12/336,562, entitled “STORAGE SECURITY USING CRYPTOGRAPHICSPLITTING”, filed 17 Dec. 2008. The present disclosure is related tocommonly assigned, U.S. patent application Ser. No. 12/336,564, entitled“STORAGE SECURITY USING CRYPTOGRAPHIC SPLITTING”, filed 17 Dec. 2008.The present disclosure is related to commonly assigned, U.S. patentapplication Ser. No. 12/336,568, entitled “STORAGE SECURITY USINGCRYPTOGRAPHIC SPLITTING”, filed 17 Dec. 2008.

The present disclosure is related to commonly assigned, and concurrentlyfiled, U.S. patent application Ser. No. 12/342,438, entitled “STORAGEAVAILABILITY USING CRYPTOGRAPHIC SPLITTING”, filed 23 Dec. 2008.

The present disclosure is related to commonly assigned, and concurrentlyfiled, U.S. patent application Ser. No. 12/342,547, entitled “STORAGE OFCRYPTOGRAPHICALLY-SPLIT DATA BLOCKS AT GEOGRAPHICALLY-SEPARATEDLOCATIONS”, filed 23 Dec. 2008. The present disclosure is related tocommonly assigned, and concurrently filed, U.S. patent application, Ser.No. 12/342,523, entitled “RETRIEVAL OF CRYPTOGRAPHICALLY-SPLIT DATABLOCKS FROM FASTEST-RESPONDING STORAGE DEVICES”, filed 23 Dec. 2008. Thepresent disclosure is related to commonly assigned, and concurrentlyfiled, U.S. patent application Ser. No. 12/342,500, entitled“BLOCK-LEVEL DATA STORAGE USING AN OUTSTANDING WRITE LIST”, filed 23Dec. 2008.

The present disclosure is related to commonly assigned, and concurrentlyfiled, U.S. patent application Ser. No. 12/342,636, entitled “STORAGECOMMUNITIES OF INTEREST USING CRYPTOGRAPHIC SPLITTING”, filed 23 Dec.2008. The present disclosure is related to commonly assigned, andconcurrently filed, U.S. patent application, Ser. No. 12/342,575,entitled “STORAGE COMMUNITIES OF INTEREST USING CRYPTOGRAPHICSPLITTING”, filed 23 Dec. 2008. The present disclosure is related tocommonly assigned, and concurrently filed, U.S. patent application Ser.No. 12/342,610, entitled “STORAGE COMMUNITIES OF INTEREST USINGCRYPTOGRAPHIC SPLITTING”, filed 23 Dec. 2008.

The present disclosure is related to commonly assigned, and concurrentlyfiled, U.S. patent application Ser. No. 12/342,379, entitled “SECURENETWORK ATTACHED STORAGE DEVICE USING CRYPTOGRAPHIC SPLITTING”, filed 23Dec. 2008.

The present disclosure is related to commonly assigned, and concurrentlyfiled, U.S. patent application Ser. No. 12/342,414, entitled “VIRTUALTAPE BACKUP ARRANGEMENT USING CRYPTOGRAPHICALLY SPLIT STORAGE”, filed 23Dec. 2008.

These related applications are incorporated by reference herein in itsentirety as if it is set forth in this application.

TECHNICAL FIELD

The present disclosure relates generally to data availability incomputer networks. In particular, the present disclosure relates tostorage availability in cryptographic splitting systems.

BACKGROUND

Modern organizations generate and store large quantities of data. Inmany instances, organizations store much of their important data at acentralized data storage system. It is frequently important that suchorganizations be able to quickly access the data stored at the datastorage system. In addition, it is frequently important that data storedat the data storage system be recoverable if the data is written to thedata storage system incorrectly or if portions of the data stored at therepository is corrupted. Furthermore, it is important that data be ableto be backed up to provide security in the event of device failure orother catastrophic event.

The large scale data centers managed by such organizations typicallyrequire mass data storage structures and storage area networks that arecapable of providing both long-term mass data storage and accesscapabilities for application servers using that data. Some data securitymeasures are usually implemented in such large data storage networks,and are intended to ensure proper data privacy and prevent datacorruption. Typically, data security is accomplished via encryption ofdata and/or access control to a network within which the data is stored.Data can be stored in one or more locations, e.g. using a redundantarray of inexpensive disks (RAID) or other techniques.

One example of an existing mass data storage system 10 is illustrated inFIG. 1. As shown, an application server 12 (e.g. a database or filesystem provider) connects to a number of storage devices 14 ₁-14 _(N)providing mass storage of data to be maintained accessible to theapplication server via direct connection 15, an IP-based network 16, anda Storage Area Network 18. Each of the storage devices 14 can host disks20 of various types and configurations useable to store this data.

The physical disks 20 are made visible/accessible to the applicationserver 12 by mapping those disks to addressable ports using, forexample, logical unit numbering (LUN), internet SCSI (iSCSI), or commoninternet file system (CIFS) connection schemes. In the configurationshown, five disks are made available to the application server 12,bearing assigned letters I-M. Each of the assigned drive letterscorresponds to a different physical disk 20 (or at least a differentportion of a physical disk) connected to a storage device 14, and has adedicated addressable port through which that disk 20 is accessible forstorage and retrieval of data. Therefore, the application server 12directly addresses data stored on the physical disks 20.

A second typical data storage arrangement 30 is shown in FIG. 2. Thearrangement 30 illustrates a typical data backup configuration useableto tape-backup files stored in a data network. The network 30 includesan application server 32, which makes a snapshot of data 34 to send to abackup server 36. The backup server 36 stores the snapshot, and operatesa tape management system 38 to record that snapshot to a magnetic tape40 or other long-term storage device.

These data storage arrangements have a number of disadvantages. Forexample, in the network 10, a number of data access vulnerabilitiesexist. An unauthorized user can steal a physical disk 20, and therebyobtain access to sensitive files stored on that disk. Or, theunauthorized user can exploit network vulnerabilities to observe datastored on disks 20 by monitoring the data passing in any of the networks15, 16, 18 between an authorized application server 12 or otherauthorized user and the physical disk 20. The network 10 also hasinherent data loss risks. In the network 30, physical data storage canbe time consuming, and physical backup tapes can be subject to failure,damage, or theft.

To overcome some of these disadvantages, systems have been introducedwhich duplicate and/or separate files and directories for storage acrossone or more physical disks. The files and directories are typicallystored or backed up as a monolith, meaning that the files are logicallygrouped with other like data before being secured. Although thisprovides a convenient arrangement for retrieval, in that a commonsecurity construct (e.g. an encryption key or password) is related toall of the data, it also provides additional risk exposure if the datais compromised.

For these and other reasons, improvements are desirable.

SUMMARY

In accordance with the following disclosure, the above and otherproblems are solved by the following:

In a first aspect, a method for maintaining data connectivity in asecure data storage network is disclosed. In one aspect, a methodincludes assigning a volume to a primary secure storage appliancelocated in a secure data storage network the primary secure storageappliance selected from among a plurality of secure storage applianceslocated in the secure data storage network, the volume presented as avirtual disk to a client device and mapped to physical storage at eachof a plurality of storage systems. The method further includes detectingat one of the plurality of secure storage appliances a failure of theprimary secure storage appliance. The method also includes, upondetecting the failure of the primary secure storage appliance,reassigning the volume to a second secure storage appliance from amongthe plurality of secure storage appliances, thereby rendering the secondsecure storage appliance a new primary secure storage appliance.

In a second aspect, a method of maintaining operation of a plurality ofsecure storage appliances is disclosed. The method includes assigning avolume to a primary secure storage appliance located in a secure datastorage network the primary secure storage appliance selected from amonga plurality of secure storage appliances located in the secure datastorage network, the volume presented as a virtual disk to a clientdevice and mapped to physical storage at each of a plurality of storagesystems. The method further includes presenting an administrativeinterface to an administrator of the secure data storage network, theadministrative interface presenting the plurality of secure storageappliances as a virtual secure storage appliance. The method alsoincludes presenting a common set of administrative settings for each ofthe plurality of secure storage appliances associated with the virtualsecure storage appliance, such that, upon detecting at one of theplurality of secure storage appliances a failure of the primary securestorage appliance, the common set of administrative settings remainaccessible to the administrator.

In a third aspect, a secure data storage network is disclosed. Thesecure data storage network includes a client device, a plurality ofstorage systems, and a plurality of secure storage appliancesinterconnected between the client device and the plurality of storagesystems, the plurality of secure storage appliances including a primarysecure storage appliance associated with a volume, the volume presentedas a virtual disk to the client device and mapped to physical storage ateach of the plurality of storage systems. In the secure data storagenetwork, each of the plurality of secure storage appliances includes acommon set of administrative information, and each of the plurality ofsecure storage appliances monitors operational status of one or more ofa different secure storage appliance among the plurality of securestorage appliances.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example prior art network providing data storage;

FIG. 2 illustrates an example prior art network providing data backupcapabilities;

FIG. 3 illustrates a data storage system according to a possibleembodiment of the present disclosure;

FIG. 4 illustrates a data storage system according to a further possibleembodiment of the present disclosure;

FIG. 5 illustrates a portion of a data storage system including a securestorage appliance, according to a possible embodiment of the presentdisclosure;

FIG. 6 illustrates a block diagram of logical components of a securestorage appliance, according to a possible embodiment of the presentdisclosure.

FIG. 7 illustrates a portion of a data storage system including a securestorage appliance, according to a further possible embodiment of thepresent disclosure;

FIG. 8 illustrates dataflow of a write operation according to a possibleembodiment of the present disclosure;

FIG. 9 illustrates dataflow of a read operation according to a possibleembodiment of the present disclosure;

FIG. 10 illustrates a further possible embodiment of a data storagenetwork including redundant secure storage appliances, according to apossible embodiment of the present disclosure;

FIG. 11 illustrates incorporation of secure storage appliances in aportion of a data storage network, according to a possible embodiment ofthe present disclosure;

FIG. 12 illustrates an arrangement of a data storage network accordingto a possible embodiment of the present disclosure;

FIG. 13 illustrates a physical block structure of data to be writtenonto a physical storage device, according to aspects of the presentdisclosure;

FIG. 14 shows a flowchart of systems and methods for providing access tosecure storage in a storage area network according to a possibleembodiment of the present disclosure;

FIG. 15 shows a flowchart of systems and methods for reading block-levelsecured data according to a possible embodiment of the presentdisclosure;

FIG. 16 shows a flowchart of systems and methods for writing block-levelsecured data according to a possible embodiment of the presentdisclosure;

FIG. 17 shows a possible arrangement for providing secure storage databackup, according to a possible embodiment of the present disclosure;

FIG. 18 shows a possible arrangement for providing secure storage for athin client computing network, according to a possible embodiment of thepresent disclosure;

FIG. 19 illustrates the data storage network arrangement of FIG. 12depicting a plurality of potential failover mechanism according to apossible embodiment of the present disclosure;

FIG. 20 shows a flowchart of systems and methods for failover accordingto a possible embodiment of the present disclosure;

FIG. 21 shows a flowchart of systems and methods for failover resultingfrom one or more communication path failures according to a possibleembodiment of the present disclosure; and

FIG. 22 shows a flowchart of systems and methods for failover resultingfrom a secure storage appliance failure according to a possibleembodiment of the present disclosure.

DETAILED DESCRIPTION

Various embodiments of the present invention will be described in detailwith reference to the drawings, wherein like reference numeralsrepresent like parts and assemblies throughout the several views.Reference to various embodiments does not limit the scope of theinvention, which is limited only by the scope of the claims attachedhereto. Additionally, any examples set forth in this specification arenot intended to be limiting and merely set forth some of the manypossible embodiments for the claimed invention.

The logical operations of the various embodiments of the disclosuredescribed herein are implemented as: (1) a sequence of computerimplemented steps, operations, or procedures running on a programmablecircuit within a computer, and/or (2) a sequence of computer implementedsteps, operations, or procedures running on a programmable circuitwithin a directory system, database, or compiler.

In general the present disclosure relates to a block-level data storagesecurity system. By block-level, it is intended that the data storageand security performed according to the present disclosure is notperformed based on the size or arrangement of logical files (e.g. on aper-file or per-directory level), but rather that the data security isbased on individual read and write operations related to physical blocksof data. In various embodiments of the present disclosure, the datamanaged by the read and write operations are split or grouped on abitwise or other physical storage level. These physical storage portionsof files can be stored in a number of separated components, andencrypted. The split, encrypted data improves data security for the data“at rest” on the physical disks, regardless of the accessvulnerabilities of physical disks storing the data. This is at least inpart because the data cannot be recognizably reconstituted withouthaving appropriate access and decryption rights to multiple, distributeddisks. The access rights limitations provided by such a system alsomakes deletion of data simple, in that deletion of access rights (e.g.encryption keys) provides for effective deletion of all data related tothose rights.

The various embodiments of the present disclosure are applicable acrossa number of possible networks and network configurations; in certainembodiments, the block-level data storage security system can beimplemented within a storage area network (SAN) or Network-AttachedStorage (NAS). Other possible networks in which such systems can beimplemented exist as well.

Referring now to FIG. 3, a block diagram illustrating an example datastorage system 100 is shown, according to the principles of the presentdisclosure. In the example of FIG. 3, system 100 includes a set ofclient devices 105A through 105N (collectively, “client devices 105”).Client devices 105 can be a wide variety of different types of devices.For example, client devices 105 can be personal computers, laptopcomputers, network telephones, mobile telephones, television set topboxes, network televisions, video gaming consoles, web kiosks, devicesintegrated into vehicles, mainframe computers, personal media players,intermediate network devices, network appliances, and other types ofcomputing devices. Client devices 105 may or may not be used directly byhuman users.

Client devices 105 are connected to a network 110. Network 110facilitates communication among electronic devices connected to network110. Network 110 can be a wide variety of electronic communicationnetworks. For example, network 110 can be a local-area network, awide-area network (e.g., the Internet), an extranet, or another type ofcommunication network. Network 110 can include a variety of connections,including wired and wireless connections. A variety of communicationsprotocols can be used on network 110 including Ethernet, WiFi, WiMax,Transfer Control Protocol, and many other communications protocols.

In addition, system 100 includes an application server 115. Applicationserver 115 is connected to the network 110, which is able to facilitatecommunication between the client devices 105 and the application server115. The application server 115 provides a service to the client devices105 via network 110. For example, the application server 115 can providea web application to the client devices 105. In another example, theapplication server 115 can provide a network-attached storage server tothe client devices 105. In another example, the application server 115can provide a database access service to the client devices 105. Otherpossibilities exist as well.

The application server 115 can be implemented in several ways. Forexample, the application server 115 can be implemented as a standaloneserver device, as a server blade, as an intermediate network device, asa mainframe computing device, as a network appliance, or as another typeof computing device. Furthermore, it should be appreciated that theapplication server 115 can include a plurality of separate computingdevices that operate like one computing device. For instance, theapplication server 115 can include an array of server blades, a networkdata center, or another set of separate computing devices that operateas if one computing device. In certain instances, the application servercan be a virtualized application server associated with a particulargroup of users, as described in greater detail below in FIG. 18.

The application server 115 is communicatively connected to a securestorage appliance 120 that is integrated in a storage area network (SAN)125. Further, the secure storage appliance 120 is communicativelyconnected to a plurality of storage devices 130A through 130N(collectively, “storage devices 130”). Similar to the secure storageappliance 120, the storage devices 130 can be integrated with the SAN125.

The secure storage appliance 120 can be implemented in several ways. Forexample, the secure storage appliance 120 can be implemented as astandalone server device, as a server blade, as an intermediate networkdevice, as a mainframe computing device, as a network appliance, or asanother type of computing device. Furthermore, it should be appreciatedthat, like the application server 115, the secure storage appliance 120can include a plurality of separate computing devices that operate likeone computing device. In certain embodiments, SAN 125 may include aplurality of secure storage appliances. Each of secure storageappliances 214 is communicatively connected to a plurality of thestorage devices 130. In addition, it should be appreciated that thesecure storage appliance 120 can be implemented on the same physicalcomputing device as the application server 115.

The application server 115 can be communicatively connected to thesecure storage appliance 120 in a variety of ways. For example, theapplication server 115 can be communicatively connected to the securestorage appliance 120 such that the application server 115 explicitlysends I/O commands to secure storage appliance 120. In another example,the application server 115 can be communicatively connected to securestorage appliance 120 such that the secure storage appliance 120transparently intercepts I/O commands sent by the application server115. On a physical level, the application server 115 and the securestorage appliance 120 can be connected via most physical interfaces thatsupport a SCSI command set. Examples of such interfaces include FibreChannel and iSCSI interfaces.

The storage devices 130 can be implemented in a variety of differentways as well. For example, one or more of the storage devices 130 can beimplemented as disk arrays, tape drives, JBODs (“just a bunch ofdisks”), or other types of electronic data storage devices.

In various embodiments, the SAN 125 is implemented in a variety of ways.For example, the SAN 125 can be a local-area network, a wide-areanetwork (e.g., the Internet), an extranet, or another type of electroniccommunication network. The SAN 125 can include a variety of connections,including wired and wireless connections. A variety of communicationsprotocols can be used on the SAN 125 including Ethernet, WiFi, WiMax,Transfer Control Protocol, and many other communications protocols. Incertain embodiments, the SAN 125 is a high-bandwidth data networkprovided using, at least in part, an optical communication networkemploying Fibre Channel connections and Fibre Channel Protocol (FCP)data communications protocol between ports of data storage computingsystems.

The SAN 125 additionally includes an administrator device 135. Theadministrator device 135 is communicatively connected to the securestorage appliance 120 and optionally to the storage devices 130. Theadministrator device 135 facilitates administrative management of thesecure storage appliance 120 and to storage devices. For example, theadministrator device 135 can provide an application that can transferconfiguration information to the secure storage appliance 120 and thestorage devices 130. In another example, the administrator device 135can provide a directory service used to store information about the SAN125 resources and also centralize the SAN 125.

In various embodiments, the administrator device 135 can be implementedin several ways. For example, the administrator device 135 can beimplemented as a standalone computing device such as a PC or a laptop,or as another type of computing device. Furthermore, it should beappreciated that, like the secure storage appliance 120, theadministrator device 135 can include a plurality of separate computingdevices that operate as one computing device.

Now referring to FIG. 4, a data storage system 200 is shown according toa possible embodiment of the present disclosure. The data storage system200 provides additional security by way of introduction of a securestorage appliance and related infrastructure/functionality into the datastorage system 200, as described in the generalized example of FIG. 3.

In the embodiment shown, the data storage system 200 includes anapplication server 202, upon which a number of files and databases arestored. The application server 202 is generally one or more computingdevices capable of connecting to a communication network and providingdata and/or application services to one or more users (e.g. in aclient-server, thin client, or local account model). The applicationserver 202 is connected to a plurality of storage systems 204. In theembodiment shown, storage systems 204 ₁₋₅ are shown, and are illustratedas a variety of types of systems including direct local storage, as wellas hosted remote storage. Each of storage systems 204 manages storage onone or more physical storage devices 206. The physical storage devices206 generally correspond to hard disks or other long-term data storagedevices. In the specific embodiment shown, the JBOD storage system 204 ₁connects to physical storage devices 206 ₁, the NAS storage system 204 ₂connects to physical storage device 206 ₂, the JBOD storage system 204 ₃connects to physical storage devices 206 ₃₋₇, the storage system 204 ₄connects to physical storage devices 206 ₈₋₁₂, and the JBOD storagesystem 204 ₅ connects to physical storage device 206 ₁₃. Otherarrangements are possible as well, and are in general a matter of designchoice.

In the embodiment shown, a plurality of different networks andcommunicative connections reside between the application server 202 andthe storage systems 204. For example, the application server 202 isdirectly connected to JBOD storage system 204 ₁ via a plurality ofphysical storage devices 208 (JBOD connection), e.g. for local storage.The application server 202 is also communicatively connected to storagesystems 204 ₂₋₃ via network 210, which uses any of a number of IP-basedprotocols such as Ethernet, WiFi, WiMax, Transfer Control Protocol, orany other of a number of communications protocols. The applicationserver 202 also connects to storage systems 204 ₄₋₅ via a storage areanetwork (SAN) 212, which can be any of a number of types of SAN networksdescribed in conjunction with SAN 125, above.

A secure storage appliance 120 is connected between the applicationserver 202 and a plurality of the storage systems 204. The securestorage appliance 120 can connect to dedicated storage systems (e.g. theJBOD storage system 204 ₅ in FIG. 4), or to storage systems connectedboth directly through the SAN 212, and via the secure storage appliance120 (e.g. the JBOD storage system 204 ₃ and storage system 204 ₄).Additionally, the secure storage appliance 120 can connect to systemsconnected via the network 210 (e.g. the JBOD storage system 204 ₃).Other arrangements are possible as well. In instances where the securestorage appliance 120 is connected to one of storage systems 204, one ormore of the physical storage devices 206 managed by the correspondingsystem is secured by way of data processing by the secure storageappliance. In the embodiment shown, the physical storage devices 206₃₋₇, 206 ₁₀₋₁₃ are secured physical storage devices, meaning that thesedevices contain data managed by the secure storage appliance 120, asexplained in further detail below.

Generally, inclusion of the secure storage appliance 120 within the datastorage system 200 may provide improved data security for data stored onthe physical storage devices. As is explained below, this can beaccomplished, for example, by cryptographically splitting the data to bestored on the physical devices, such that generally each device containsonly a portion of the data required to reconstruct the originally storeddata, and that portion of the data is a block-level portion of the dataencrypted to prevent reconstitution by unauthorized users.

Through use of the secure storage appliance 120 within the data storagesystem 200, a plurality of physical storage devices 208 can be mapped toa single volume, and that volume can be presented as a virtual disk foruse by one or more groups of users. In comparing the example datastorage system 200 to the prior art system shown in FIG. 1, it can beseen that the secure storage appliance 120 allows a user to have anarrangement other than one-to-one correspondence between drive volumeletters (in FIG. 1, drive letters I-M) and physical storage devices. Inthe embodiment shown, two additional volumes are exposed to theapplication server 202, virtual disk drives T and U, in which securecopies of data can be stored. Virtual disk having volume label T isillustrated as containing secured volumes F3 and F7 (i.e. the drivesmapped to the iSCSI2 port of the application server 202, as well as anew drive), thereby providing a secured copy of information on either ofthose drives for access by a group of users. Virtual disk having volumelabel U provides a secured copy of the data held in DB1 (i.e. the drivemapped to LUN03). By distributing volumes across multiple disks,security is enhanced because copying or stealing data from a singlephysical disk will generally be insufficient to access that data (i.e.multiple disks of data, as well as separately-held encryption keys, mustbe acquired)

Referring now to FIG. 5, a portion of the data storage system 200 isshown, including details of the secure storage appliance 120. In theembodiment shown, the secure storage appliance 120 includes a number offunctional modules that generally allow the secure storage appliance tomap a number of physical disks to one or more separate, accessiblevolumes that can be made available to a client, and presenting a virtualdisk to clients based on those defined volumes. Transparently to theuser, the secure storage appliance applies a number of techniques tostored and retrieved data to provide data security.

In the embodiment shown, the secure storage appliance 120 includes acore functional unit 216, a LUN mapping unit 218, and a storagesubsystem interface 220. The core functional unit 216 includes a dataconversion module 222 that operates on data written to physical storagedevices 206 and retrieved from the physical storage devices 206. Ingeneral, when the data conversion module 222 receives a logical unit ofdata (e.g. a file or directory) to be written to physical storagedevices 206, it splits that primary data block at a physical level (i.e.a “block level”) and encrypts the secondary data blocks using a numberof encryption keys.

The manner of splitting the primary data block, and the number ofphysical blocks produced, is dictated by additional control logic withinthe core functional unit 216. As described in further detail below,during a write operation that writes a primary data block to physicalstorage (e.g. from an application server 202), the core functional unit216 directs the data conversion module 222 to split the primary datablock received from the application server 202 into N separate secondarydata blocks. Each of the N secondary data blocks is intended to bewritten to a different one of physical storage devices 206 within thedata storage system 200. The core functional unit 216 also dictates tothe data conversion module 222 the number of shares (for example,denoted as M of the N total shares) that are required to reconstitutethe primary data block when requested by the application server 202.

The secure storage appliance 120 connects to a metadata store 224, whichis configured to hold metadata information about the locations,redundancy, and encryption of the data stored on the physical storagedevices 206. The metadata store 224 is generally held locally or inproximity to the secure storage appliance 120, to ensure fast access ofmetadata regarding the shares. The metadata store 224 can be, in variousembodiments, a database or file system storage of data describing thedata connections, locations, and shares used by the secure storageappliance. Additional details regarding the specific metadata stored inthe metadata store 224 are described below.

The LUN mapping unit 218 generally provides a mapping of one or morephysical storage devices 206 to a volume. Each volume corresponds to aspecific collection of physical storage devices 206 upon which the datareceived from client devices is stored. In contrast, typical prior artsystems assign a LUN (logical unit number) or other identifier to eachphysical storage device or connection port to such a device, such thatdata read operations and data write operations directed to one ofstorage systems 204 can be performed specific to a device associatedwith the system. In the embodiment shown, the LUNs correspond to targetaddressable locations on the secure storage appliance 120, of which oneor more is exposed to a client device, such as an application server202. Based on the mapping of LUNs to a volume, the virtual disk relatedto that volume appears as a directly-addressable component of the datastorage system 200, having its own LUN. From the perspective of theapplication server 202, this obscures the fact that primary data blockswritten to a volume can in fact be split, encrypted, and written to aplurality of physical storage devices across one or more storage systems204.

The storage subsystem interface 220 routes data from the core functionalunit 216 to the storage systems 204 communicatively connected to thesecure storage appliance 120. The storage subsystem interface 220 allowsaddressing various types of storage systems 204. Other functionality canbe included as well.

In the embodiment shown, a plurality of LUNs are made available by theLUN mapping unit 218, for addressing by client devices. As shown by wayof example, LUNs LUN04-LUNnn are illustrated as being addressable byclient devices. Within the core functional unit 216, the data conversionmodule 222 associates data written to each LUN with a share of thatdata, split into N shares and encrypted. In the embodiment shown in theexample of FIG. 5, a block read operation or block write operation toLUN04 is illustrated as being associated with a four-way write, in whichsecondary data blocks L04.a through L04.d are created, and mapped tovarious devices connected to output ports, shown in FIG. 5 as networkinterface cards (NICs), a Fibre Channel interface, and a serial ATAinterface. An analogous operation is also shown with respect to LUN05,but written to a different combination of shares and correspondingphysical disks.

The core functional unit 216, LUN mapping unit 218, and storagesubsystem interface 220 can include additional functionality as well,for managing timing and efficiency of data read and write operations.Additional details regarding this functionality are described in anotherembodiment, detailed below in conjunction with the secure storageappliance functionality described in FIG. 6.

The secure storage appliance 120 includes an administration interface226 that allows an administrator to set up components of the securestorage appliance 120 and to otherwise manage data encryption,splitting, and redundancy. The administration interface 226 handlesinitialization and discovery on the secure storage appliance, as well ascreation, modifying, and deletion of individual volumes and virtualdisks; event handling; data base administration; and other systemservices (such as logging). Additional details regarding usage of theadministration interface 226 are described below in conjunction withFIG. 14.

In the embodiment shown of the secure storage appliance 120, the securestorage appliance 120 connects to an optional enterprise directory 228and a key manager 230 via the administration interface 226. Theenterprise directory 228 is generally a central repository forinformation about the state of the secure storage appliance 120, and canbe used to help coordinate use of multiple secure storage appliances ina network, as illustrated in the configuration shown in FIG. 10, below.The enterprise directory 228 can store, in various embodiments,information including a remote user table, a virtual disk table, ametadata table, a device table, log and audit files, administratoraccounts, and other secure storage appliance status information.

In embodiments lacking the enterprise directory 228, redundant securestorage appliances 214 can manage and prevent failures by storing statusinformation of other secure storage appliances, to ensure that eachappliance is aware of the current state of the other appliances.

The key manager 230 stores and manages certain keys used by the datastorage system 200 for encrypting data specific to various physicalstorage locations and various individuals and groups accessing thosedevices. In certain embodiments, the key manager 230 stores workgroupkeys. Each workgroup key relates to a specific community of individuals(i.e. a “community of interest”) and a specific volume, thereby defininga virtual disk for that community. The key manager 230 can also storelocal copies of session keys for access by the secure storage appliance120. Secure storage appliance 120 uses each of the session keys tolocally encrypt data on different ones of physical storage devices 206.Passwords can be stored at the key manager 230 as well. In certainembodiments, the key manager 230 is operable on a computing systemconfigured to execute any of a number of key management softwarepackages, such as the Key Management Service provided for a WindowsServer environment, manufactured by Microsoft Corp. of Redmond, Wash.

Although the present disclosure provides for encryption keys includingsession keys and workgroup keys, additional keys may be used as well,such as a disk signature key, security group key, client key, or othertypes of keys. Each of these keys can be stored on one or more ofphysical storage devices 206, at the secure storage appliance 120, or inthe key manager 230.

Although FIGS. 4-5 illustrate a particular arrangement of a data storagesystem 200 for secure storage of data, additional arrangements arepossible as well that can operate consistently with the concepts of thepresent disclosure. For example, in certain embodiments, the system caninclude a different number or type of storage systems or physicalstorage devices, and can include one or more different types of clientsystems in place of or in addition to the application server 202.Furthermore, the secure storage appliance 120 can be placed in any of anumber of different types of networks, but does not require the presenceof multiple types of networks as illustrated in the example of FIG. 4.

FIG. 6 is a block diagram that illustrates example logical components ofthe secure storage appliance 120. FIG. 6 represents only one example ofthe logical components of the secure storage appliance 120, forperforming the operations described herein. The operations of the securestorage appliance 120 can be conceptualized and implemented in manydifferent ways.

As illustrated in the example of FIG. 6, the secure storage appliance120 comprises a primary interface 300 and a secondary interface 302. Theprimary interface 300 enables secure storage appliance 120 to receiveprimary I/O requests and to send primary I/O responses. For instance,the primary interface 300 can enable secure storage appliance 120 toreceive primary I/O requests (e.g. read and write requests) from theapplication server device 202 and to send primary I/O responses to theapplication server 202. Secondary interface enables the secure storageappliance 120 to send secondary I/O requests to the storage systems 204,and to receive secondary I/O responses from those storage systems 204.

In addition, the secure storage appliance 120 comprises a parser driver304. The parser driver 304 generally corresponds to the data conversionmodule 222 of FIG. 5, in that it processes primary I/O requests togenerate secondary I/O requests and processes secondary I/O responses togenerate primary I/O responses. To accomplish this, the parser driver304 comprises a read module 305 that processes primary read requests togenerate secondary read requests and processes secondary read responsesto generate primary read responses. In addition, the parser driver 304comprises a decryption module 308 that enables the read module 305 toreconstruct a primary data block using secondary blocks contained insecondary read responses. Example operations performed by the readmodule 305 are described below with reference to FIGS. 15, 22, and 24.Furthermore, the parser driver 304 comprises a write module 306 thatprocesses primary write requests to generate secondary write requestsand processes secondary write responses to generate primary writeresponses. The parser driver 304 also comprises an encryption module 310that enables the write module 306 to cryptographically split primarydata blocks in primary write requests into secondary data blocks to putin secondary write requests. An example operation performed by the writemodule 306 is described below as well with reference to FIGS. 16, 23,and 25.

In the example of FIG. 6, the secure storage appliance 120 alsocomprises a cache driver 315. When enabled, the cache driver 315receives primary I/O requests received by the primary interface 300before the primary I/O requests are received by parser driver 304. Whenthe cache driver 315 receives a primary read request to read data at aprimary storage location of a virtual disk, the cache driver 315determines whether a write-through cache 316 at the secure storageappliance 120 contains a primary write request to write a primary datablock to the primary storage location of the virtual disk. If the cachedriver 315 determines that the write-through cache 316 contains aprimary write request to write a primary data block to the primarystorage location of the virtual disk, the cache driver 315 outputs aprimary read response that contains the primary data block. When theparser driver 304 receives a primary write request to write a primarydata block to a primary storage location of a virtual disk, the cachedriver 315 caches the primary write request in the write-through cache316. A write-through module 318 performs write operations to memory fromthe write-through cache 316.

The secure storage appliance 120 also includes an outstanding write list(OWL) module 326. When enabled, the OWL module 326 receives primary I/Orequests from the primary interface 300 before the primary I/O requestsare received by the parser driver 304. The OWL module 326 uses anoutstanding write list 320 to process the primary I/O requests.

In addition, the secure storage appliance 120 comprises a backup module324. The backup module 324 performs an operation that backs up data atthe storage systems 204 to backup devices, as described below inconjunction with FIGS. 17-18.

The secure storage appliance 120 also comprises a configuration changemodule 312. The configuration change module 312 performs an operationthat creates or destroys a volume, and sets its redundancyconfiguration. Example redundancy configurations (i.e. “M of N”configurations) are described throughout the present disclosure, andrefer to the number of shares formed from a block of data, and thenumber of those shares required to reconstitute the block of data.Further discussion is provided with respect to possible redundancyconfigurations below, in conjunction with FIGS. 8-9.

It should be appreciated that many alternate implementations of thesecure storage appliance 120 are possible. For example, a firstalternate implementation of the secure storage appliance 120 can includethe OWL module 326, but not the cache driver 315, or vice versa. Inother examples, the secure storage appliance 120 might not include thebackup module 324 or the configuration change module 312. Furthermore,there can be many alternate operations performed by the various modulesof the secure storage appliance 120.

FIG. 7 illustrates further details regarding connections to andoperational hardware and software included in secure storage appliance120, according to a possible embodiment of the present disclosure. Thesecure storage appliance 120 illustrates the various operationalhardware modules available in the secure storage appliance to accomplishthe data flow and software module operations described in FIGS. 4-6,above. In the embodiment shown, the secure storage appliance 120 iscommunicatively connected to a client device 402, an administrativeconsole 404, a key management server 406, a plurality of storage devices408, and an additional secure storage appliance 120′.

In the embodiment shown, the secure storage appliance 120 connects tothe client device 402 via both an IP network connection 401 and a SANnetwork connection 403. The secure storage appliance 120 connects to theadministrative console 404 by one or more IP connections 405 as well.The key management server 406 is also connected to the secure storageappliance 120 by an IP network connection 407. The storage devices 408are connected to the secure storage appliance 120 by the SAN networkconnection 403, such as a Fibre Channel or other high-bandwidth dataconnection. Finally, in the embodiment shown, secure storage appliances120 and 120′ are connected via any of a number of types of communicativeconnections 411, such as an IP or other connection, for communicatingheartbeat messages and status information for coordinating actions ofthe secure storage appliance 120 and the secure storage appliance 120′.Although in the embodiment shown, these specific connections and systemsare included, the arrangement of devices connected to the secure storageappliance 120, as well as the types and numbers of devices connected tothe appliance may be different in other embodiments.

The secure storage appliance 120 includes a number of software-basedcomponents, including a management service 410 and a system managementmodule 412. The management service 410 and the system management module412 each connect to the administrative console 404 or otherwise providesystem management functionality for the secure storage appliance 120.The management service 410 and system management module 412 aregenerally used to set various settings in the secure storage appliance120, view logs 414 stored on the appliance, and configure other aspectsof a network including the secure storage appliance 120. Additionally,the management service 410 connects to the key management server 406,and can request and receive keys from the key management server 406 asneeded.

A cluster service 416 provides synchronization of state informationbetween the secure storage appliance 120 and secure storage appliance120′. In certain embodiments, the cluster service 416 manages aheartbeat message and status information exchanged between the securestorage appliance 120 and the secure storage appliance 120′. Securestorage appliance 120 and secure storage appliance 120′ periodicallyexchange heartbeat messages to ensure that secure storage appliance 120and secure storage appliance 120′ maintain contact. Secure storageappliance 120 and secure storage appliance 120′ maintain contact toensure that the state information received by each secure storageappliance indicating the state of the other secure storage appliance isup to date. An active directory services 418 stores the statusinformation, and provides status information periodically to othersecure storage appliances via the communicative connections 411.

Additional hardware and/or software components provide datapathfunctionality to the secure storage appliance 120 to allow receipt ofdata and storage of data at the storage devices 408. In the embodimentshown, the secure storage appliance 120 includes a SNMP connectionmodule 420 that enables secure storage appliance 120 to communicate withclient devices via the IP network connection 401, as well as one or morehigh-bandwidth data connection modules, such as a Fibre Channel inputmodule 422 or SCSI input module 424 for receiving data from the clientdevice 402 or storage devices 408. Analogous data output modulesincluding a Fibre Channel connection module 421 or SCSI connectionmodule 423 can connect to the storage devices 408 or client device 402via the SAN network connection 403 for output of data.

Additional functional systems within the secure storage appliance 120assist in datapath operations. A SCSI command module 425 parses andforms commands to be sent out or received from the client device 402 andstorage devices 408. A multipath communications module 426 provides ageneralized communications interface for the secure storage appliance120, and a disk volume 428, disk 429, and cache 316 provide local datastorage for the secure storage appliance 120.

Additional functional components can be included in the secure storageappliance 120 as well. In the embodiment shown, a parser driver 304provides data splitting and encryption capabilities for the securestorage appliance 120, as previously explained. A provider 434 includesvolume management information, for creation and destruction of volumes.An events module 436 generates and handles events based on observedoccurrences at the secure storage appliance (e.g. data errors orcommunications errors with other systems).

FIGS. 8-9 provide a top level sense of a dataflow occurring during writeand read operations, respectively, passing through a secure storageappliance, such as the secure storage appliance described above inconjunction with FIGS. 3-7. FIG. 8 illustrates a dataflow of a writeoperation according to a possible embodiment of the present disclosure,while FIG. 9 illustrates dataflow of a read operation. In the writeoperation of FIG. 8, a primary data block 450 is transmitted to a securestorage appliance (e.g. from a client device such as an applicationserver). The secure storage appliance can include a functional block 460to separate the primary data block into N secondary data blocks 470,shown as S-1 through S-N. In certain embodiments, the functional block460 is included in a parser driver, such as parser driver 304, above.The specific number of secondary data blocks can vary in differentnetworks, and can be defined by an administrative user having access tocontrol settings relevant to the secure storage appliance. Each of thesecondary data blocks 470 can be written to separate physical storagedevices. In the read operation of FIG. 9, M secondary data blocks areaccessed from physical storage devices, and provided to the functionalblock 460 (e.g. parser driver 304). The functional block 460 thenperforms an operation inverse to that illustrated in FIG. 8, therebyreconstituting the primary data block 450. The primary data block canthen be provided to the requesting device (e.g. a client device).

In each of FIGS. 8-9, the N secondary data blocks 470 each represent acryptographically split portion of the primary data block 450, such thatthe functional block 460 requires only M of the N secondary data blocks(where M<=N) to reconstitute the primary data block 450. Thecryptographic splitting and data reconstitution of FIGS. 8-9 can beperformed according to any of a number of techniques. In one embodiment,the parser driver 304 executes SecureParser software provided bySecurity First Corporation of Rancho Santa Margarita, Calif.

Although, in the embodiment shown in FIG. 9, the parser driver 304 usesthe N secondary data blocks 470 to reconstitute the primary data block450, it is understood that in certain applications, fewer than all ofthe N secondary data blocks 470 are required. For example, when theparser driver 304 generates N secondary data blocks during a writeoperation such that only M secondary data blocks are required toreconstitute the primary data block (where M<N), then data conversionmodule 60 only needs to read that subset of secondary data block fromphysical storage devices to reconstitute the primary data block 450.

For example, during operation of the parser driver 304 a data conversionroutine may generate four secondary data blocks 470, of which two areneeded to reconstitute a primary data block (i.e. M=2, N=4). In such aninstance, two of the secondary data blocks 470 may be stored locally,and two of the secondary data blocks 470 may be stored remotely toensure that, upon failure of a device or catastrophic event at onelocation, the primary data block 450 can be recovered by accessing oneor both of the secondary data blocks 470 stored remotely. Otherarrangements are possible as well, such as one in which four secondarydata blocks 470 are stored locally and all are required to reconstitutethe primary data block 450 (i.e. M=4, N=4). At its simplest, a singleshare could be created (M=N=1).

FIG. 10 illustrates a further possible embodiment of a data storagesystem 250, according to a possible embodiment of the presentdisclosure. The data storage system 250 generally corresponds to thedata storage system 200 of FIG. 4, above, but further includes redundantsecure storage appliances 214. Each of secure storage appliances 214 maybe an instance of secure storage appliance 120. Inclusion of redundantsecure storage appliances 214 allows for load balancing of read andwrite requests in the data storage system 250, such that a single securestorage appliance is not required to process every secure primary readcommand or primary write command passed from the application server 202to one of the secure storage appliances 214. Use of redundant securestorage appliances also allows for failsafe operation of the datastorage system 250, by ensuring that requests made of a failed securestorage appliance are rerouted to alternative secure storage appliances.

In the embodiment of the data storage system 250 shown, two securestorage appliances 214 are shown. Each of the secure storage appliances214 can be connected to any of a number of clients (e.g. the applicationserver 202), as well as secured storage systems 204, the metadata store224, and a remote server 252. In various embodiments, the remote server252 could be, for example, an enterprise directory 228 and/or a keymanager 230.

The secure storage appliances 214 are also typically connected to eachother via a network connection. In the embodiment shown in the exampleof FIG. 10, the secure storage appliances 214 reside within a network254. In various embodiments, network 254 can be, for example, anIP-based network, SAN as previously described in conjunction with FIGS.4-5, or another type of network. In certain embodiments, the network 254can include aspects of one or both types of networks. An example of aparticular configuration of such a network is described below inconjunction with FIGS. 11-12.

The secure storage appliances 214 in the data storage system 250 areconnected to each other across a TCP/IP portion of the network 254. Thisallows for the sharing of configuration data, and the monitoring ofstate, between the secure storage appliances 214. In certain embodimentsthere can be two IP-based networks, one for sharing of heartbeatinformation for resiliency, and a second for configuration andadministrative use. The secure storage appliance 120 can alsopotentially be able to access the storage systems 204, including remotestorage systems, across an IP network using a data interface.

In operation, sharing of configuration data, state data, and heartbeatinformation between the secure storage appliances 214 allows the securestorage appliances 214 to monitor and determine whether other securestorage appliances are present within the data storage system 250. Eachof the secure storage appliances 214 can be assigned specific addressesof read operations and write operations to process. Secure storageappliances 214 can reroute received I/O commands to the appropriate oneof the secure storage appliances 214 assigned that operation based uponthe availability of that secure storage appliance and the resourcesavailable to the appliance. Furthermore, the secure storage appliances214 can avoid addressing a common storage device 204 or applicationserver 202 port at the same time, thereby avoiding conflicts. The securestorage appliances 214 also avoid reading from and writing to the sameshare concurrently to prevent the possibility of reading stale data.

When one of the secure storage appliances 214 fails, a second securestorage appliance can determine the state of the failed secure storageappliance based upon tracked configuration data (e.g. data trackedlocally or stored at the remote server 252). The remaining operationalone of the secure storage appliances 214 can also access information inthe metadata store 224, including share and key information definingvolumes, virtual disks and client access rights, to either process orreroute requests assigned to the failed device.

As previously described, the data storage system 250 is intended to beexemplary of a possible network in which aspects of the presentdisclosure can be implemented; other arrangements are possible as well,using different types of networks, systems, storage devices, and othercomponents.

Referring now to FIG. 11, one possibility of a methodology ofincorporating secure storage appliances into a data storage network,such as a SAN, is shown according to a possible embodiment of thepresent disclosure. In the embodiment shown, a secure storage network500 provides for fully redundant storage, in that each of the storagesystems connected at a client side of the network is replicated in massstorage, and each component of the network (switches, secure storageappliances) is located in a redundant array of systems, therebyproviding a failsafe in case of component failure. In alternativeembodiments, the secure storage network 500 can be simplified byincluding only a single switch and/or single secure storage appliance,thereby reducing the cost and complexity of the network (whilecoincidentally reducing the protection from component failure).

In the embodiment shown, an overall secure storage network 500 includesa plurality of data lines 502 a-d interconnected by switches 504 a-b.Data lines 502 a-b connect to storage systems 506 a-c, which connect tophysical storage disks 508 a-f. The storage systems 506 a-c correspondgenerally to smaller-scale storage servers, such as an applicationserver, client device, or other system as previously described. In theembodiment shown in the example of FIG. 11, storage system 506 aconnects to physical storage disks 508 a-b, storage system 506 bconnects to physical storage disks 508 c-d, and storage system 506 cconnects to physical storage disks 508 e-f. The secure storage network500 can be implemented in a number of different ways, such as throughuse of Fibre Channel or iSCSI communications as the data lines 502 a-d,ports, and other data communications channels. Other high bandwidthcommunicative connections can be used as well.

The switches 504 a-b connect to a large-scale storage system, such asthe mass storage 510 via the data lines 502 c-d. The mass storage 510includes, in the embodiment shown, two data directors 512 a-b, whichrespectively direct data storage and requests for data to one or more ofthe back end physical storage devices 514 a-d. In the embodiment shown,the physical storage devices 514 a-c are unsecured (i.e. notcryptographically split and encrypted), while the physical storagedevice 514 d stores secure data (i.e. password secured or otherarrangement).

The secure storage appliances 516 a-b also connect to the data lines 502a-d, and each connect to the secure physical storage devices 518 a-e.Additionally, the secure storage appliances 516 a-b connect to thephysical storage devices 520 a-c, which can reside at a remote storagelocation (e.g. the location of the large-scale storage system massstorage 510).

In certain embodiments providing redundant storage locations, the securestorage network 500 allows a user to configure the secure storageappliances 516 a-b such that, using the M of N cryptographic splittingenabled in each of the secure storage appliances 516 a-b, M shares ofdata can be stored on physical storage devices at a local location toprovide fast retrieval of data, while another M shares of data can bestored on remote physical storage devices at a remote location.Therefore, failure of one or more physical disks or secure storageappliances does not render data unrecoverable, because a sufficientnumber of shares of data remain accessible to at least one securestorage appliance capable of reconstituting requested data.

FIG. 12 illustrates a particular cluster-based arrangement of a datastorage network 600 according to a possible embodiment of the presentdisclosure. The data storage network 600 is generally arranged such thatclustered secure storage appliances access and store shares on clusteredphysical storage devices, thereby ensuring fast local storage and accessto the cryptographically split data. The data storage network 600 istherefore a particular arrangement of the networks and systems describedabove in FIGS. 1-11, in that it represents an arrangement in whichphysical proximity of devices is accounted for.

In the embodiment shown, the data storage network 600 includes twoclusters, 602 a-b. Each of the clusters 602 a-b includes a pair ofsecure storage appliances 604 a-b, respectively. In the embodimentshown, the clusters 602 a-b are labeled as clusters A and B,respectively, with each cluster including two secure storage appliances604 a-b (shown as appliances A1 and A2 in cluster 602 a, and appliancesB1 and B2 in cluster 602 b, respectively). The secure storage appliances604 a-b within each of the clusters 602 a-b are connected via a datanetwork 605 (e.g. via switches or other data connections in an iSCSI,Fibre Channel, or other data network, as described above and indicatedvia the nodes and connecting lines shown within the data network 605) toa plurality of physical storage devices 610. Additionally, the securestorage appliances 604 a-b are connected to client devices 612, shown asclient devices C1-C3, via the data network 605. The client devices 612can be any of a number of types of devices, such as application servers,database servers, or other types of data-storing and managing clientdevices.

In the embodiment shown, the client devices 612 are connected to thesecure storage appliances 604 a-b such that each of client devices 612can send I/O operations (e.g. a read request or a write request) to twoor more of the secure storage appliances 604 a-b, to ensure a backupdatapath in case of a connection failure to one of secure storageappliances 604 a-b. Likewise, the secure storage appliances 604 a-b ofeach of clusters 602 a-b are both connected to a common set of physicalstorage devices 610. Although not shown in the example of FIG. 12, thephysical storage devices 610 can be, in certain embodiments, managed byseparate storage systems, as described above. Such storage systems areremoved from the illustration of the data storage network 600 forsimplicity, but can be present in practice.

An administrative system 614 connects to a maintenance console 616 via alocal area network 618. Maintenance console 616 has access to a secureddomain 620 of an IP-based network 622. The maintenance console 616 usesthe secured domain 620 to access and configure the secure storageappliances 604 a-b. One method of configuring the secure storageappliances is described below in conjunction with FIG. 14.

The maintenance console 616 is also connected to both the client devices612 and the physical storage devices 610 via the IP-based network 622.The maintenance console 616 can determine the status of each of thesedevices to determine whether connectivity issues exist, or whether thedevice itself has become non-responsive.

Referring now to FIG. 13, an example physical block structure of datawritten onto one or more physical storage devices is shown, according toaspects of the present disclosure. The example of FIG. 13 illustratesthree strips 700A, 700B, and 700C (collectively, “shares”). Each ofstrips 700 is a share of a physical storage device devoted to storingdata associated with a common volume. For example, in a system in whicha write operation splits a primary data block into three secondary datablocks (i.e. N=3), the strips 700 (shares) would be appropriately usedto store each of the secondary data blocks. As used in this disclosure,a volume is grouped storage that is presented by a secure storageappliance to clients of secure storage appliance (e.g. secure storageappliance 120 or one of secure storage appliances 214 as previouslydescribed), such that the storage appears as a contiguous, unitarystorage location. Secondary data blocks of a volume are distributedamong strips 700. In systems implementing a different number of shares(e.g. N=2, 4, 6, etc.), a different, corresponding number of shareswould be used. As basic as a 1 of 1 configuration (M=1, N=1)configuration could be used.

Each of the strips 700 corresponds to a reserved portion of memory of adifferent one of physical storage devices (e.g. physical storage devices206 previously described), and relates to a particular I/O operationfrom storage or reading of data to/from the physical storage device.Typically, each of the strips 700 resides on a different one of physicalstorage devices. Furthermore, although three different strips are shownin the illustrative embodiment shown, more or fewer strips can be usedas well. In certain embodiments, each of the strips 700 begins on asector boundary. In other arrangements, the each of the strips 700 canbegin at any other memory location convenient for management within theshare.

Each of strips 700 includes a share label 704, a signature 706, headerinformation 708, virtual disk information 710, and data blocks 712. Theshare label 704 is written on each of strips 700 in plain text, andidentifies the volume and individual share. The share label 704 canalso, in certain embodiments, contain information describing otherheader information for the strips 700, as well as the origin of the datawritten to the strip (e.g. the originating cluster).

The signature 706 contain information required to construct the volume,and is encrypted by a workgroup key. The signatures 706 containinformation that can be used to identify the physical device upon whichdata (i.e. the share) is stored. The workgroup key corresponds to a keyassociated with a group of one or more users having a common set ofusage rights with respect to data (i.e. all users within the group canhave access to common data.) In various embodiments, the workgroup keycan be assigned to a corporate department using common data, a commongroup of one or more users, or some other community of interest for whomcommon access rights are desired.

The header information 708 contains session keys used to encrypt anddecrypt the volume information included in the virtual disk information710, described below. The header information 708 is also encrypted bythe workgroup key. In certain embodiments, the header information 708includes headers per section of data. For example, the headerinformation 708 may include one header for each 64 GB of data. In suchembodiments, it may be advantageous to include at least one empty headerlocation to allow re-keying of the data encrypted with a preexistingsession key, using a new session key.

The virtual disk information 710 includes metadata that describes avirtual disk, as it is presented by a secure storage appliance. Thevirtual disk information 710, in certain embodiments, includes names topresent the virtual disk, a volume security descriptor, and securitygroup information. The virtual disk information 710 can be, in certainembodiments, encrypted by a session key associated with the physicalstorage device upon which the strips 700 are stored, respectively.

The secondary data blocks 712 correspond to a series of memory locationsused to contain the cryptographically split and encrypted data. Each ofthe secondary data blocks 712 contains data created at a secure storageappliance, followed by metadata created by the secure storage applianceas well. The N secondary data blocks created from a primary data blockare combined to form a stripe 714 of data. The metadata stored alongsideeach of the secondary data blocks 712 contains an indicator of theheader used for encrypting the data. In one example implementation, eachof the secondary data blocks 712 includes metadata that specifies anumber of times that the secondary data block has been written. A volumeidentifier and stripe location of an primary data block an be stored aswell.

It is noted that, although a session key is associated with a volume,multiple session keys can be used per volume. For example, a volume mayinclude one session key per 64 GB block of data. In this example, each64 GB block of data contains an identifier of the session key to use indecrypting that 64 GB block of data. The session keys used to encryptdata in each of strips 700 can be of any of a number of forms. Incertain embodiments, the session keys use an AES-256 Counter with BitSplitting. In other embodiments, it may be possible to perform bitsplitting without encryption.

A variety of access request prioritization algorithms can be includedfor use with the volume, to allow access of only quickest-respondingphysical storage devices associated with the volume. Status informationcan be stored in association with a volume and/or share as well, withchanges in status logged based on detection of event occurrences. Thestatus log can be located in a reserved, dedication portion of memory ofa volume. Other arrangements are possible as well.

It is noted that, based on the encryption of session keys with workgroupkeys and the encryption of the secondary data blocks 712 in each ofstrips 700 with session keys, it is possible to effectively delete allof the data on a disk or volume (i.e. render the data useless) bydeleting all workgroup keys that could decrypt a session key for thatdisk or volume.

Referring now to FIGS. 14-16, basic example flowcharts of setup and useof the networks and systems disclosed herein are described. Althoughthese flowcharts are intended as example methods for administrative andI/O operations, such operations can include additional steps/modules,can be performed in a different order, and can be associated withdifferent number and operation of modules. In certain embodiments, thevarious modules can be executed concurrently.

FIG. 14 shows a flowchart of systems and methods 800 for providingaccess to secure storage in a storage area network according to apossible embodiment of the present disclosure. The systems and methods800 correspond to a setup arrangement for a network including a securedata storage system such as those described herein, including one ormore secure storage appliances. The embodiments of the systems andmethods described herein can be performed by an administrative user oradministrative software associated with a secure storage appliance, asdescribed herein.

Operational flow is instantiated at a start operation 802, whichcorresponds to initial introduction of a secure storage appliance into anetwork by an administrator or other individuals of such a network in aSAN, NAS, or other type of networked data storage environment.Operational flow proceeds to a client definition module 804 that definesconnections to client devices (i.e. application servers or otherfront-end servers, clients, or other devices) from the secure storageappliance. For example, the client definition module 804 can correspondto mapping connections in a SAN or other network between a client suchas application server 202 and a secure storage appliance 120 of FIG. 4.

Operational flow proceeds to a storage definition module 806. Thestorage definition module 806 allows an administrator to defineconnections to storage systems and related physical storage devices. Forexample, the storage definition module 806 can correspond to discoveringports and routes to storage systems 204 within the system 200 of FIG. 4,above.

Operational flow proceeds to a volume definition module 808. The volumedefinition module 808 defines available volumes by grouping physicalstorage into logical arrangements for storage of shares of data. Forexample, an administrator can create a volume, and assign a number ofattributes to that volume. A storage volume consists of multiple sharesor segments of storage from the same or different locations. Theadministrator can determine a number of shares into which data iscryptographically split, and the number of shares required toreconstitute that data. The administrator can then assign specificphysical storage devices to the volume, such that each of the N sharesis stored on particular devices. The volume definition module 808 cangenerate session keys for storing data on each of the physical storagedevices, and store that information in a key server and/or on thephysical storage devices. In certain embodiments, the session keysgenerated in the volume definition module 808 are stored both on a keyserver connected to the secure storage appliance and on the associatedphysical storage device (e.g. after being encrypted with an appropriateworkgroup key generated by the communities of interest module 810,below). Optionally, the volume definition module 808 includes acapability of configuring preferences for which shares are firstaccessed upon receipt of a request to read data from those shares.

Operational flow proceeds to a communities of interest module 810. Thecommunities of interest module 810 corresponds to creation of one ormore groups of individuals having interest in data to be stored on aparticular volume. The communities of interest module 810 module furthercorresponds to assigning of access rights and visibility to volumes toone or more of those groups.

In creating the groups via the communities of interest module 810, oneor more workgroup keys may be created, with each community of interestbeing associated with one or more workgroup keys. The workgroup keys areused to encrypt access information (e.g. the session keys stored onvolumes created during operation of the volume definition module 808)related to shares, to ensure that only individuals and devices fromwithin the community of interest can view and access data associatedwith that group. Once the community of interest is created andassociated with a volume, client devices identified as part of thecommunity of interest can be provided with a virtual disk, which ispresented to the client device as if it is a single, unitary volume uponwhich files can be stored.

In use, the virtual disks appear as physical disks to the client andsupport SCSI or other data storage commands. Each virtual disk isassociated on a many-to-one basis with a volume, thereby allowingmultiple communities of interest to view common data on a volume (e.g.by replicating the relevant session keys and encrypting those keys withrelevant workgroup keys of the various communities of interest). A writecommand will cause the data to be encrypted and split among multipleshares of the volume before writing, while a read command will cause thedata to be retrieved from the shares, combined, and decrypted.

Operational flow terminates at end operation 812, which corresponds tocompletion of the basic required setup tasks to allow usage of a securedata storage system.

FIG. 15 shows a flowchart of systems and methods 820 for readingblock-level secured data according to a possible embodiment of thepresent disclosure. The systems and methods 820 correspond to a read orinput command related to data stored via a secure storage appliance,such as those described herein. Operational flow in the system andmethods 820 begins at a start operation 822. Operational flow proceedsto a receive read request module 824, which corresponds to receipt of aprimary read request at a secure storage appliance from a client device(e.g. an application server or other client device, as illustrated inFIGS. 3-4). The read request generally includes an identifier of avirtual disk from which data is to be read, as well as an identifier ofthe requested data.

Operational flow proceeds to an identity determination module 826, whichcorresponds to a determination of the identity of the client from whichthe read request is received. The client's identity generallycorresponds with a specific community of interest. This assumes that theclient's identity for which the secure storage appliance will access aworkgroup key associated with the virtual disk that is associated withthe client.

Operational flow proceeds to a share determination module 828. The sharedetermination module 828 determines which shares correspond with avolume that is accessed by way of the virtual disk presented to the userand with which the read request is associated. The shares correspond toat least a minimum number of shares needed to reconstitute the primarydata block (i.e. at least M of the N shares). In operation, a readmodule 830 issues secondary read requests to the M shares, and receivesin return the secondary data blocks stored on the associated physicalstorage devices.

A success operation 832 determines whether the read module 830successfully read the secondary data blocks. The success operation maydetect for example, that data has been corrupted, or that a physicalstorage device holding one of the M requested shares has failed, orother errors. If the read is successful, operational flow branches “yes”to a reconstitute data module 834. The reconstitute data module 834decrypts a session key associated with each share with the workgroup keyaccessed by the identity determination module 826. The reconstitute datamodule 834 provides the session key and the encrypted andcryptographically split data to a data processing system within thesecure storage appliance, which reconstitutes the requested data in theform of an unencrypted block of data physical disk locations inaccordance with the principles described above in FIGS. 8-9 and 13. Aprovide data module 836 sends the reconstituted block of data to therequesting client device. A metadata update module 838 updates metadataassociated with the shares, including, for example, access informationrelated to the shares. From the metadata update module 838, operationalflow proceeds to an end operation 840, signifying completion of the readrequest.

If the success operation 832 determines that not all of the M shares aresuccessfully read, operational flow proceeds to a supplemental readoperation 842, which determines whether an additional share exists fromwhich to read data. If such a share exists (e.g. M<N), then thesupplemental read operation reads that data, and operational flowreturns to the success operation 832 to determine whether the system hasnow successfully read at least M shares and can reconstitute the primarydata block as requested. If the supplemental read operation 842determines that no further blocks of data are available to be read (e.g.M=N or M+failed reads>N), operational flow proceeds to a fail module844, which returns a failed read response to the requesting clientdevice. Operational flow proceeds to the metadata update module 838 andend operation 840, respectively, signifying completion of the readrequest.

Optionally, the fail module 844 can correspond to a failover event inwhich a backup copy of the data (e.g. a second N shares of data storedremotely from the first N shares) are accessed. In such an instance,once those shares are tested and failed, a fail message is sent to aclient device.

In certain embodiments, commands and data blocks transmitted to theclient device can be protected or encrypted, such as by using apublic/private key or symmetric key encryption techniques, or byisolating the data channel between the secure storage appliance andclient. Other possibilities exist for protecting data passing betweenthe client and secure storage appliance as well.

Furthermore, although the system and methods 820 of FIG. 15 illustratesa basic read operation, it is understood that certain additional casesrelated to read errors, communications errors, or other anomalies mayoccur which can alter the flow of processing a read operation. Forexample, additional considerations may apply regarding which M of the Nshares to read from upon initially accessing physical storage devices206. Similar considerations apply with respect to subsequent secondaryread requests to the physical storage devices in case those readrequests fail as well.

FIG. 16 shows a flowchart of systems and methods 850 for writingblock-level secured data according to a possible embodiment of thepresent disclosure. The systems and methods 850 as disclosed provide abasic example of a write operation, and similarly to the read operationof FIG. 15 additional cases and different operational flow may be used.

In the example systems and methods 850 disclosed, operational flow isinstantiated at a start operation 852. Operational flow proceeds to awrite request receipt module 854, which corresponds to receiving aprimary write request from a client device (e.g. an application serveras shown in FIGS. 3-4) at a secure storage appliance. The primary writerequest generally addresses a virtual disk, and includes a block of datato be written to the virtual disk.

Operational flow proceeds to an identity determination module 856, whichdetermines the identity of the client device from which the primarywrite request is received. After determining the identity of the clientdevice, the identity determination module 856 accesses a workgroup keybased upon the identity of the client device and accesses the virtualdisk at which the primary write request is targeted. Operational flowproceeds to a share determination module 858, which determines thenumber of secondary data blocks that will be created, and the specificphysical disks on which those shares will be stored. The sharedetermination module 858 obtains the session keys for each of the sharesthat are encrypted with the workgroup key obtained in the identitydetermination module 856 (e.g. locally, from a key manager, or from thephysical disks themselves). These session keys for each share aredecrypted using the workgroup key.

Operational flow proceeds to a data processing module 860, whichprovides to the parser driver 304 the share information, session keys,and the primary data block. The parser driver 304 operates tocryptographically split and encrypt the primary data block, therebygenerating N secondary data blocks to be written to N shares inaccordance with the principles described above in the examples of FIGS.8-9 and 13. Operational flow proceeds to a secondary write module 862which transmits the share information to the physical storage devicesfor storage.

Operational flow proceeds to a metadata storage module 864, whichupdates a metadata repository by logging the data written, allowing thesecure storage appliance to track the physical disks upon which data hasbeen written, and with what session and workgroup keys the data can beaccessed. Operational flow terminates at an end operation 866, whichsignifies completion of the write request.

As previously mentioned, in certain instances additional operations canbe included in the system and methods 850 for writing data using thesecure storage appliance. For example, confirmation messages can bereturned to the secure storage appliance confirming successful storageof data on the physical disks. Other operations are possible as well.

Now referring to FIGS. 17-18 of the present disclosure, certainapplications of the present disclosure are discussed in the context of(1) data backup systems and (2) secure network thin client networktopology used in the business setting. FIG. 17 shows an example system900 for providing secure storage data backup, according to a possibleembodiment of the present disclosure. In the system 900 shown, a virtualtape server 902 is connected to a secure storage appliance 904 via adata path 906, such as a SAN network using Fibre Channel or iSCSIcommunications. The virtual tape server 902 includes a management system908, a backup subsystem interface 910, and a physical tape interface912. The management system 908 provides an administrative interface forperforming backup operations. The backup subsystem interface 910receives data to be backed up onto tape, and logs backup operations. Aphysical tape interface 912 queues and coordinates transmission of datato be backed up to the secure storage appliance 904 via the network. Thevirtual tape server 902 is also connected to a virtual tape managementdatabase 914 that stores data regarding historical tape backupoperations performed using the system 900.

The secure storage appliance 904 provides a virtual tape head assembly916 which is analogous to a virtual disk but appears to the virtual tapeserver 902 to be a tape head assembly to be addressed and written to.The secure storage appliance 904 connects to a plurality of tape headdevices 918 capable of writing to magnetic tape, such as that typicallyused for data backup. The secure storage appliance 904 is configured asdescribed above. The virtual tape head assembly 916 provides aninterface to address data to be backed up, which is thencryptographically split and encrypted by the secure storage applianceand stored onto a plurality of distributed magnetic tapes using the tapehead devices 918 (as opposed to a generalized physical storage device,such as the storage devices of FIGS. 3-4).

In use, a network administrator could allocate virtual disks that wouldbe presented to the virtual tape head assembly 916. The virtual tapeadministrator would allocate these disks for storage of data receivedfrom the client through the virtual tape server 902. As data is writtento the disks, it would be cryptographically split and encrypted via thesecure storage appliance 904.

The virtual tape administrator would present virtual tapes to a network(e.g. an IP or data network) from the virtual tape server 902. The datain storage on the tape head devices 918 is saved by the backup functionsprovided by the secure storage appliance 904. These tapes are mapped tothe virtual tapes presented by the virtual tape head assembly 916.Information is saved on tapes as a collection of shares, as previouslydescribed.

An example of a tape backup configuration illustrates certain advantagesof a virtual tape server over the standard tape backup system asdescribed above in conjunction with FIG. 2. In one example of a tapebackup configuration, share 1 of virtual disk A, share 1 of virtual diskB, and other share 1's can be saved to a tape using the tape headdevices 918. Second shares of each of these virtual disks could bestored to a different tape. Keeping the shares of a virtual tapeseparate preserves the security of the information, by distributing thatinformation across multiple tapes. This is because more than one tape isrequired to reconstitute data in the case of a data restoration. Datafor a volume is restored by restoring the appropriate shares from therespective tapes. In certain embodiments an interface that canautomatically restore the shares for a volume can be provided for thevirtual tape assembly. Other advantages exist as well.

Now referring to FIG. 18, one possible arrangement of a thin clientnetwork topology is shown in which secure storage is provided. In thenetwork 950 illustrated, a plurality of thin client devices 952 areconnected to a consolidated application server 954 via a secured networkconnection 956.

The consolidated application server 954 provides application and datahosting capabilities for the thin client devices 952. In addition, theconsolidated application server 954 can, as in the example embodimentshown, provide specific subsets of data, functionality, and connectivityfor different groups of individuals within an organization. In theexample embodiment shown, the consolidated application server 954 canconnect to separate networks and can include separate, dedicated networkconnections for payroll, human resources, and finance departments. Otherdepartments could have separate dedicated communication resources, data,and applications as well. The consolidated application server 954 alsoincludes virtualization technology 958, which is configured to assist inmanaging separation of the various departments' data and applicationaccessibility.

The secured network connection 956 is shown as a secure Ethernetconnection using network interface cards 957 to provide networkconnectivity at the server 954. However, any of a number of secure datanetworks could be implemented as well.

The consolidated application server 954 is connected to a secure storageappliance 960 via a plurality of host bus adapter connections 961. Thesecure storage appliance 960 is generally arranged as previouslydescribed in FIGS. 3-16. The host bus adapter connections 961 allowconnection via a SAN or other data network, such that each of thededicated groups on the consolidated application server 954 has adedicated data connection to the secure storage appliance 960, andseparately maps to different port logical unit numbers (LUNs). Thesecure storage appliance 960 then maps to a plurality of physicalstorage devices 962 that are either directly connected to the securestorage appliance 960 or connected to the secure storage appliance 960via a SAN 964 or other data network.

In the embodiment shown, the consolidated application server 954 hosts aplurality of guest operating systems 955, shown as guest operatingsystems 955 a-c. The guest operating systems 955 hostuser-group-specific applications and data for each of the groups ofindividuals accessing the consolidated application server. Each of theguest operating systems 955 a-c have virtual LUNs and virtual NICaddresses mapped to the LUNs and NIC addresses within the server 954,while virtualization technology 958 provides a register of the mappingsof LUNS and NIC addresses of the server 954 to the virtual LUNs andvirtual NIC addresses of the guest operating systems 955 a-c. Throughthis arrangement, dedicated guest operating systems 955 can be mapped todedicated LUN and NIC addresses, while having data that is isolated fromthat of other groups, but shared across common physical storage devices962.

As illustrated in the example of FIG. 18, the physical storage devices962 provide a typical logistical arrangement of storage, in which a fewstorage devices are local to the secure storage appliance, while a fewof the other storage devices are remote from the secure storageappliance 960. Through use of (1) virtual disks that are presented tothe various departments accessing the consolidated application server954 and (2) shares of virtual disks assigned to local and remotestorage, each department can have its own data securely stored across aplurality of locations with minimal hardware redundancy and improvedsecurity.

Although FIGS. 17-18 present a few options for applications of thesecure storage appliance and secure network storage of data as describedin the present disclosure, it is understood that further applicationsare possible as well. Furthermore, although each of these applicationsis described in conjunction with a particular network topology, it isunderstood that a variety of network topologies could be implemented toprovide similar functionality, in a manner consistent with theprinciples described herein.

Now referring to FIGS. 19-22, certain aspects of the present disclosureare described in the context of failover such that data availability anddata integrity are maintained despite failure of one or more computernetwork elements. The term “failover” as used herein refers to a failurerecovery mechanism implemented in response to a removal of a redundantcomputer network element from functional operational service. In oneaspect, failover can be in response to a voluntary action, such as forexample an administrator taking a secure storage appliance off-line formaintenance. In most instances, failover in response to a voluntaryaction is not accompanied by potential issues relating to dataavailability and integrity. In contrast, an involuntary failover, suchas in response to a spontaneous hardware or communication path failure,can potentially result in a compromise of data availability and/orsecurity.

FIG. 19 depicts additional data storage network 600, as described abovewith reference to FIG. 12, to articulate failover and failovertechniques according to the principles of the present disclosure. Asdescribed above, network 600 is only one example arrangement of anetwork and system in which one or more features and/or elements of thepresent disclosure may be implemented. Thus, it will be appreciated thatthe following description and example embodiments apply to a wide rangeof networks and systems configured accordingly. Particularly, tonetworks and systems in which a secure storage appliance provides, inpart, a block-level cryptographic data splitting service.

As described above, network 600 is a cluster-based computer networkarrangement in which two clusters, 602 a-b are provided with a pair ofsecure storage appliances 604 a-b, respectively. A data network 605, aspreviously described, can, as shown, include a front-end network 605 aand a back-end network 605. A plurality of client devices 612 areconnected to the clusters 602 a-b via the data network 605, shown inFIG. 19 as front-end network 605 a. Further, a common set of physicalstorage devices 610 are located within each cluster 604 a-b, the storagedevices 610 accessible to the pair of secure storage appliances 604 a-bvia the data network 605, shown in FIG. 19 as back-end network 605 b. Ingeneral, each respective client device 612 can send an I/O operationassociated with a volume (e.g., a read or write request) to at least onesecure storage appliance 604 via front-end network 605 a as desired.Subsequently, the I/O operation is executed by a respective securestorage appliances 604 via retrieval and/or storage of data on thecommon set of physical storage devices 610 over a back-end network 605b.

In the example embodiment, the front-end network 605 a includes aplurality of I/O communication paths between secure storage appliances604 and clients 612 in which each respective client 612 represents avalid I/O communication path to any secure storage appliance 604 innetwork 600. Each I/O communication path of front-end network 605 a canconfigured so that only a properly configured client 612 can see and/orinterpret the data that is transferred therethrough. Further, back-endnetwork 605 b includes a plurality of I/O communication paths arrangedbetween a respective secure storage appliance 604 and one or morestorage devices 610. Other configurations are possible as well.

Generally, the architecture and the various functional elements ofnetwork 600 introduce redundancy such that implementation of failovercan occur between at least one of (1) a first cluster and a secondcluster; and (2) a first secure storage appliance and a second securestorage appliance within a respective cluster. In this manner, I/Ooperation execution can proceed despite computer network element failureevents while further maintaining data security. It will be appreciatedthat the level of redundancy is in general a matter of design choice.

In one example embodiment, in the context of element (1) above, cluster602 a and cluster 602 b can be configured to be fully redundant suchthat in an event in which one of the respective clusters is renderednon-operational and/or portions of a respective cluster areinaccessible, failover to the remaining operational cluster can occur.For example, cluster 602 a can be configured to operate as a localizedprimary cluster for client devices 612 to provide high-speed access tocryptographically split data stored on storage devices 610. In theexample embodiment, cluster 602 b can be configured to operate as aback-up to cluster 602 a, in which the data stored on storage devices610 in cluster 602 a are periodically duplicated on storage devices 610of back-up cluster 602 b. In this manner, redundancy is provided suchthat an failure event related to cluster 602 a would not render datastored on respective storage devices 610 inaccessible.

For example, one mechanism that can require failover from the primarycluster 602 a to the back-up cluster 602 b may include a communicationpath failure in front-end network 605 a that would render secure storageappliances 604 a-b of cluster 602 a inaccessible. In the exampleembodiment, the described mechanism is designated by “X₁” overlaid on aportion of front-end network 605 a. A second failover mechanism that canrequire the described failover may include a complete failure of I/Ocommunications paths of back-end network 605 b, such that data stored instorage elements 610 is rendered inaccessible to respective securestorage appliances 604 a-b. In the example embodiment, this describedfailover mechanism is designated by “X₂” overlaid on a central node ofback-end network 605 b. Further, a third failover mechanism that canrequire the described failover may include a partial failure of I/Ocommunications paths in back-end network 605 b. In the exampleembodiment, failover would be required if requisite M of N shares (orequivalently, storage devices 610) are inaccessible and therefore an I/Ooperation cannot be executed, designated by “X₃” overlaid on a portionof back-end network 605 b.

In general, upon detection of the example failure mechanisms representedby scenarios X₁, X₂, and X₃, an assessment of the failure can be madeand I/O messages can be rerouted to backup cluster 602 b for processing,described in further detail below with reference to FIGS. 20-22. Incertain embodiments, cluster 602 b can be remotely located with respectto cluster 602 a to provide an additional level of protection.

In one example embodiment, in the context of element (2) above, failoverfrom a first secure storage appliance to a second secure storageappliance within a respective cluster is provided. In one exampleembodiment, a failure event that can initiate failover from a firstsecure storage appliance to a second secure storage appliance mayinclude a failure of an I/O communication path between a secure storageappliance configured as a primary secure storage appliance and arespective client. In general, a secure storage appliance is configuredas a primary secure storage appliance by assigning a volume to arespective secure storage appliance, the respective secure storageappliance selected from among a plurality of secure storage appliances.In the example embodiment, the volume is presented as a virtual disk toa client device and mapped to physical storage at each of a plurality ofstorage systems.

For example, secure storage appliance 604 a in cluster 602 a can beconfigured as a primary secure storage appliance for a virtual disk “L”as presented to client C1 612. In the event that a physicalcommunication path between secure storage appliance 604 a and client C1612 fail (designated by “X₄” overlaid on portion of front-end network605 a), failover to secure storage appliance 604 b can occur, therebyrendering secure storage appliance 604 b as a new primary secure storageappliance for virtual disk “L”.

An alternate example failure event that can initiate failover from aprimary secure storage appliance to a secondary secure storage appliancemay include the failure of a primary secure storage appliance. Forexample, in an example application, the secure storage appliance 604 ain cluster 602 b can be configured as a primary secure storage appliancefor virtual disk “M” presented to client C3 612. In the example, upondetecting at one of a plurality of secure storage appliances a failureof the primary secure storage appliance (designated by “X₅′” overlaid onsecure storage appliance 604 a in cluster 602 b) failover to securestorage appliance 604 b can occur, thereby rendering secure storageappliance 604 b as a new primary secure storage appliance for virtualdisk “M”.

In general, upon detection of the example failure mechanisms representedby scenarios X₄ and X₅, an assessment of the failure can initially bemade, and upon a determination to proceed with failover, a volume can bereassigned to a secondary secure storage appliance, thereby renderingthe second secure storage appliance a new primary storage appliance, asdescribed in further detail below with reference to FIGS. 20-22.

In the example embodiments, the clustered configuration and securestorage appliances of network 600 enables failover to occur such thatblock level I/O message processing on an individual virtual disk basisremains uninterrupted and uncorrupted. In general, coordination amongrespective secure storage appliances is enabled via a plurality ofadministrative settings stored in a configuration database required tofacilitate failover and restoration in a wide variety of failurescenarios. In example embodiments, the administrative settings provideeach respective secure storage appliance with network configurationinformation, such as configuration of primary and secondary securestorage appliance. For example, in one embodiment, each respectivecluster 602 a-b may be provided with a configuration database, 624 and626, respectively. In the example embodiment, the respectiveconfiguration databases 624, 626 are duplicated between all securestorage appliances within a respective cluster 602 a-b. In an exampleapplication in which data stored within storage device 610 is duplicatedbetween respective clusters 602 a-b, configuration databases 624, 626would be equivalent, as described in further detail below. In thismanner, if any one secure storage appliance is off-line, the remainingonline secure storage appliances can continue operation with a localcopy of the configuration database. Further, when the off-line securestorage appliance becomes available, its configuration database can berestored either via a download from another secure storage appliance inthe respective cluster, or from administrator device (e.g., console 616)storing an equivalent database, as described below.

In certain embodiments, a database service can provide a repository forconfiguration information, such as Active Directory provided for aWindows Server environment, manufactured by Microsoft Corp. of Redmond,Wash.

The administrative settings can configured by an administrator 614 viaan administrative interface 628 on console 616. In certain embodiments,the administrative interface further presents the respective securestorage appliances arranged in cluster 602 a-b as a virtual securestorage appliance, such that the configuration of the each respectiveprimary and secondary secure storage appliance is transparent. Further,the administrative settings can be associated with the virtual securestorage appliance such that upon a failure of a secure storageappliance, the common set of settings remain accessible to theadministrator.

Referring now to FIG. 20, systems and methods 2000 for implementing abasic failover between a primary secure storage appliance and asecondary secure storage appliance in a multi-path computer network isprovided according to principles of the present disclosure. In general,the example failover as described maintains data connectivity in asecure storage network. In certain embodiments, the multi-path computernetwork is a clustered computer network as described with reference toFIGS. 12 and 19. In this manner, failover can generally occur betweensecure storage appliances located in separate clusters or between securestorage appliances located within similar cluster. Further, the securestorage appliance of the disclosed systems and methods 2000 provide ablock-level cryptographic data splitting service as described in partwith reference to FIGS. 8-9, 15-16 and further throughout the presentdisclosure.

In the example systems and methods 2000 disclosed, operational flow isinstantiated at a start operation 2002. In one embodiment, startoperation 2002 corresponds to a one or more elements of the multi-pathcomputer network coming on-line, such as for example the primary andsecondary secure storage appliance and a plurality of further respectivesecure storage appliances, storage devices, client devices, andadministrator device.

In one example embodiment, the primary secure storage appliance isconfigured by an administrator via an administrative interface (e.g., aswould have been hosted on administrator device 614 of FIGS. 12 and 19)as the primary appliance by assigning a volume to the primary securestorage appliance, the volume being presented as a virtual disk to arespective client device and mapped to physical storage at one or morestorage devices. Further, in the example embodiment, the secondarysecure storage appliance can be configured by the administrator as thesecondary. In certain embodiments, the administrative interface presentsthe primary, secondary, and remaining plurality of secure storageappliances as a virtual secure storage appliance such that eachrespective secure storage appliance can be dynamically configured.

Operational flow proceeds to a receive read/write request module 2004.Receive read/write request module 2004 corresponds to receipt a blocklevel I/O message associated with a specific volume (the I/O messageconsisting of one of a read request and a write request) from arespective client device (e.g. an application server as shown in FIGS.3-4). The receive read/write request module 2004 can operate, in certainembodiments, on a secure storage appliance within a computer network, asdescribed above.

Operational flow proceeds to a determination module 2006. In one aspect,determination module 2006 corresponds to identifying the client devicefrom which the block level I/O message is received and making adetermination if the secure storage appliance receiving the data requestis the assigned primary secure storage appliance for the respectivevolume associated with the block level I/O message. In one embodiment,the determination is made by accessing a local copy of a configurationdatabase in which a plurality of common network administrative settingsof the plurality of secure storage appliances associated with a virtualsecure storage appliance are defined on an individual virtual diskbasis, including settings related to primary and secondary securestorage appliance configuration.

Upon a positive determination at determination module 2006, indicatingthat the block level I/O message was received by the primary securestorage appliance, operational flow branches “Yes” and proceeds to anexecute request evaluation module 2008. Execute request evaluationmodule 2008 in one aspect corresponds to receiving, at a primary securestorage appliance, the block level I/O message as transferred from atransfer request module 2018. In a second aspect, operational flow torequest evaluation module 2008 occurs via a positive determination atdetermination module 2006, as described above. In one embodiment,request evaluation module 2008 corresponds to a determination if theblock level I/O message can be successfully executed. In one aspect, thedetermination is made via an assessment of the operational status of aplurality of elements in the network. For example, an evaluation of theoperational status of a plurality of relevant I/O communication paths inthe network can be made, described in further detail with respect toFIGS. 21-22.

Returning now to determination module 2006, upon a negativedetermination at the determination module 2006, indicating that theblock level I/O message was received by a secondary secure storageappliance, operational flow branches “No” and proceeds to a transferevaluation module 2016. Transfer evaluation module 2016 corresponds to adetermination if the secondary secure storage appliance should transferthe block I/O message to the identified primary secure storageappliance. In certain embodiments, transfer evaluation module 2016determines if the receipt of a block I/O message for the identifiedprimary secure storage appliance is a reoccurring event, therebysuggesting the primary storage device is offline or unable to processthe block I/O message. Other evaluations are possible as well.

Upon a positive determination at transfer evaluation module 2016,indicating a decision to transfer the block I/O message to theidentified primary secure storage appliance, operational flow branches“Yes” and proceeds to transfer request module 2018 which transfers, orforwards, the block level I/O message to the as identified primarysecure storage appliance. Thereafter, upon a successful transfer of theblock level I/O message to the designated primary secure storageappliance at transfer request module 2018, operational flow proceedsexecute request evaluation module 2008. Upon a negative determination attransfer evaluation module 2016 operational flow branches “No” andproceeds to a failover module 2020.

Returning to request evaluation module 2008, upon a negativedetermination at request evaluation module 2008, indicating that theblock level I/O message cannot be successfully executed, operationalflow branches “No” and proceeds to failover module 2020. In oneembodiment, execution of failover module 2020 corresponds to thetransfer of the block level I/O message to a secondary secure storageappliance as identified via accessing a local copy of a networkconfiguration database. The described actions of failover module 2020can further be executed upon transfer of operational flow upon anegative determination at transfer evaluation module 2016, as describedabove. In the example embodiment, a successful failover corresponds toreassigning of the volume associated with the block I/O message to asecondary secure appliance and disassociating the respective volume fromthe primary secure storage appliance, thereby rendering the secondarysecure appliance a new primary secure storage appliance.

Upon execution of the transfer of the block level I/O message to thesecondary secure storage appliance at failover module 2020, operationalflow proceeds back to request evaluation module 2008 such that anevaluation can occur to determine if the block level I/O message can beexecuted by the secondary secure storage appliance, as described above.Operational flow continues between request evaluation module 2008 andfailover module 2020 until a valid failover can occur in which the blocklevel I/O message can be successfully executed.

Upon a positive determination at request evaluation module 2008,indicating that the block level I/O message can be successfullyexecuted, operational flow branches “Yes” and proceeds to a processread/write request module 2010 in which the block level I/O message isprocessed. In the context of a write operation, read/write processmodule 2010 operates to cryptographically split and encrypt the blocklevel I/O message, as described above in FIGS. 8 and 16. In the contextof a read operation, read/write process module 2010 operates to accessand decrypt data on a block level I/O, in further accordance with theprinciples described above with reference to FIGS. 9 and 15.

Upon completion of the block level I/O message processing read/writeprocess module 2010, operational flow proceeds to error process module2012. Error process module 2012 operates to determine if at least onefailover event was executed at failover module 2020. Upon a negativedetermination at error process module 2010 operational flow branches“No” and proceeds to end operation 2014. Upon a positive determinationat error process module 2012, operational flow branches “Yes” andproceeds to transfer error module 2022. Transfer error module 2022operates to transfer an error message to an administrator device of thenetwork. Following a successful operation at transfer error module 2022,operational flow proceeds to end operation 2014, which corresponds totermination of the example systems and methods 2000.

Referring now to FIG. 21, systems and methods 2100 for implementing afailover from a primary secure storage appliance to a secondary securestorage appliance in a multi-path computer network based on I/Ocommunication path failure is provided according to principles of thepresent disclosure. The disclosed systems and methods 2100 enablefailover on an individual volume basis via monitoring of a plurality ofI/O communication paths in the computer network. In certain embodiments,the multi-path computer network is a clustered computer network asdescribed with reference to FIGS. 12 and 19. In this manner, failovermay generally occur between secure storage appliances located inseparate clusters or between secure storage appliances located withinsimilar cluster. Further, the secure storage appliance of the disclosedsystems and methods 2100 provide a block-level cryptographic datasplitting service as described in part with reference to FIGS. 8-9,15-16 and further throughout the present disclosure.

In the example systems and methods 2100, operational flow isinstantiated at a start operation 2102. In one embodiment, startoperation 2102 corresponds to one or more elements of the multi-pathcomputer network coming on-line, such as for example the primary andsecondary secure storage appliance, and a plurality of furtherrespective secure storage appliances, storage devices, client devices,and administrator device.

In one embodiment, the primary secure storage appliance is configured atthe administrator device via an administrative interface as the primarysecure storage appliance by assigning a volume to the primary securestorage appliance, the volume being presented as a virtual disk to arespective client device and mapped to physical storage at one or morestorage devices. In a similar manner, the secondary secure storageappliance can be configured as such by the administrator. Further, incertain embodiments, the administrative interface presents the primary,and remaining non-primary secure storage appliances as a single virtualsecure storage appliance. In the example embodiment, the virtual securestorage appliance presents a common set of administrative settings foreach of the plurality of secure storage appliances associated with thevirtual secure storage appliance, the common set of administrativesettings remaining accessible to the administrator despite a failure ofa respective secure storage appliance.

Further, a plurality of I/O communication paths between the securestorage appliances and clients in the network are provided, in whicheach respective client represents a valid I/O path to any of theplurality of secure storage appliances. Further still, a plurality ofI/O communication paths between respective secure storage appliances andstorage devices are provided.

Operational flow proceeds to a monitor I/O path module 2104. Monitor I/Opath module 2104 corresponds to each of the plurality of secureappliance servers in the network periodically evaluating the status ofthe plurality of I/O communication paths in the network. In a firstaspect, monitor I/O path module 2104 monitors and records theoperational status of a plurality of front-end network I/O paths betweena primary secure storage appliance and a respective client device thatassociates a virtual disk therewith. In a second aspect, I/O path module2104 periodically monitors and records the operational status of aplurality of back-end network I/O paths between a primary secure storageappliance and one or more storage devices. Upon a negative determinationat monitor I/O path module 2104, indicative of no I/O path failures inthe front-end network and/or the back-end I/O network, operational flowbranches “No” and proceeds to monitor I/O path module 2104 for asubsequent I/O path evaluation after a predetermined time period. Upon apositive determination at monitor I/O path module 2104, indicating atleast one front-end and/or back-end I/O path failure, operational flowbranches “Yes” and proceeds to a failover evaluation module 2106.

Failover evaluation module 2106 corresponds to an evaluation of theseverity or extent of the at least one front-end and/or back-end I/Opath failure as assessed at monitor I/O path module 2104. In the contextof a front-end I/O path failure, failover evaluation module 2106proceeds to make a determination if a potential I/O message as presentedby the client can be received by the primary secure storage appliancevia at least one I/O path in the front-end network. In the exampleembodiment, a positive evaluation at failover evaluation module 2106would indicate that a potential I/O message as presented by the clientwould not be received by the designated primary secure storageappliance, and operational flow branches “Yes” and proceeds to anexecute failover module 2108.

Upon a negative determination at failover evaluation module 2106,indicating that a potential I/O message as presented by the client wouldeventually be received by the designated primary secure storageappliance, operational flow branches “No” and proceeds to an errormessage transfer module 2122, which transfers or forwards an errormessage to the administrator such that the I/O path failure can beaddressed. Upon successful transmission of the error message at errormessage transfer module 2122, operational flow proceeds to monitor I/Opath module 2104 to continue a periodic I/O path evaluation, asdescribed above.

In the context of a back-end I/O path failure, failover evaluationmodule 2106 proceeds to make a determination of the total number storagedevices that are positively accessible by the primary secure storageappliance, such that in the event that a potential I/O message aspresented by the client would require access to a designated number ofstorage devices greater than the total number of accessible storagedevices, a failover would be required. For example, if an I/O messagerequires access to M of N shares to reconstruct a volume, yet the numberof relevant accessible storage devices is less than M, a failover wouldbe required to maintain data availability, and operational flow wouldproceed to execute failover module 2108 for immediate action. Upon anegative determination at failover evaluation module 2106, indicatingthat a potential I/O message as presented by the client would beexecutable based on the total number of accessible storage devices, afailover would be not required and operational flow branches “No” andproceeds to the error message transfer module 2122, which transfers orforwards an error message to the administrator such that the I/O pathfailure can be addressed, as described above.

Returning to failover evaluation module 2106 in which a positivedetermination is made, thereby indicating: a) a front-end network basedfailure such that a potential I/O message as presented by the clientwould not be received by the designated primary secure storageappliance; or b): a back-end network based failure such that a potentialI/O message as presented by the client would require access to adesignated number of storage devices greater than the total number ofaccessible storage devices, operational flow branches “Yes” and proceedsto execute failover module 2108. Execute failover module 2108corresponds to the transfer of an inquiry message to a first secondarysecure appliance to determine if the first secondary secure appliance iscapable of being assigned a respective volume associated with thepotential I/O message. In one embodiment, the determination is made viaaccessing a local copy of a network configuration database in which acommon set of administrative settings, such as primary and secondarysecure storage appliance configurations, are defined on an individualvolume basis.

Upon a successful transmission of the inquiry message to the firstsecondary secure appliance at execute failover module 2108, operationalflow proceeds to a failover evaluation module 2110. In one embodiment,failover evaluation module 2110 corresponds to a determination if apotential block level I/O message can be successfully executed by thefirst secondary secure appliance. In one aspect, the determination ismade via an assessment of the operational status of a plurality ofelements in the multi-path network. For example, an evaluation can beperformed to determine the operational status of relevant front-end 605a and back-end 605 b I/O communication paths to determine if a blocklevel I/O message can be executed. Other diagnostic network analysis maybe considered as well.

Upon a positive determination at failover evaluation module 2110,operational flow branches “Yes” and proceeds to a failover proceedmodule 2112, in which the volume is reassigned such that the firstsecondary secure appliance is rendered as the new primary secure storageappliance, and further disassociating the respective volume from theprimary secure storage appliance. Upon a negative determination failoverevaluation module 2110, indicating that a potential block level I/Omessage cannot be successfully executed by the first secondary secureappliance, operational flow branches “No” and proceeds to a backupfailover attempt module 2124. Backup failover attempt module 2124corresponds to a transfer of an inquiry message from a secondary secureappliance to an alternate secondary secure appliance. In one exampleembodiment, the alternate secondary secure appliance is identified viaaccessing a local copy of a network configuration database, as describedabove. Upon a successful transmission of the inquiry message from firstsecondary secure appliance to an alternate secondary secure appliance atbackup failover attempt module 2124, operational flow proceeds back tofailover evaluation module 2110. Operational flow continues betweenfailover evaluation module 2110 and backup failover attempt module 2124until it is determined that a valid failover can occur.

Returning now to determination failover evaluation module 2110 in whicha positive determination is made, operational flow branches “Yes” andproceeds to failover proceed module 2112. As described above, failoverproceed module 2112 corresponds to reassignment of the volume to asecondary secure storage appliance such that the secondary securestorage appliance is rendered as the new primary secure storageappliance. Further the respective volume is disassociated from theprimary secure storage appliance. In certain embodiments, failoverproceed module 2112 further corresponds to the secondary secure storageappliance configuring one or more secure front-end network data paths tothe respective client and configuring one or more secure back-end datapaths to one or more storage devices, such that an I/O may besuccessfully executed. Upon successful execution of a plurality ofoperations at failover proceed module 2112, operational flow proceeds toan error message transfer module 2114, which transfers or forwards anerror message to the administrator such that the I/O path failure andfailover can be addressed and/or investigated.

Upon successful transmission of the error message at error messagetransfer module 2114, operational flow proceeds to restore operationmodule 2116. In certain embodiments, restore operation module 2116corresponds to a restoration of operation of the failed secure storageappliance, and possible restoration of the failed secure storageappliance as the primary secure storage appliance for the respectivevolume. Operational flow proceeds to a copy database module 2118. Copydatabase module 2118 corresponds to a transfer of a copy of an updatedconfiguration database to the failed primary secure storage appliance asrestored at restore operation module 2116. In certain embodiments, copydatabase module 2118 is executed at the secondary secure storageappliance that assumed the role as the new primary secure storageappliance detects the restoration of the failed secure storage applianceat restore operation module 2116. Subsequently, the secondary securestorage appliance transfers a copy of the updated configuration databaseto the newly operational secure storage appliance. In other embodiments,the updated configuration database can be transferred to the newlyoperational secure storage appliance by an administrator device (e.g.,the administrator device 614 of FIGS. 12 and 19). Following a successfuloperation at copy database module 2118, indicating the restored securestorage appliance has obtained an updated configuration database,operational flow proceeds to end operation 2120, which corresponds totermination of the example systems and methods 2100.

Referring now to FIG. 22, systems and methods 2200 for implementing afailover between a primary secure storage appliance and a secondarysecure storage appliance in a multi-path computer network based on aprimary secure storage appliance failure is provided according toprinciples of the present disclosure. The disclosed systems and methods2200 enable failover on an individual virtual disk basis by monitoringprimary secure storage appliance operational status with a heartbeatsignal. Further, the secure storage appliance of the disclosed systemsand methods 2200 provide a block-level cryptographic data splittingservice as described in part with reference to FIGS. 8-9, 15-16 andfurther throughout the present disclosure.

In the example systems and methods 2200, operational flow isinstantiated at a start operation 2202. In one embodiment, startoperation 2202 corresponds to one or more elements of the multi-pathcomputer network coming on-line, such as for example the primary andsecondary secure storage appliance, and a plurality of furtherrespective secure storage appliances, storage devices, client devices,and administrator device.

In one embodiment, the primary secure storage appliance is configured atthe administrator device via an administrative interface as the primarysecure storage appliance by assigning a volume to the primary securestorage appliance, the volume being presented as a virtual disk to arespective client device and mapped to physical storage at one or morestorage devices. In a similar manner, the secondary secure storageappliance can be configured as such by the administrator. Further, incertain embodiments, the administrative interface presents the primary,secondary, and remaining plurality of secure storage appliances as asingle virtual secure storage appliance. In the example embodiment, thevirtual secure storage appliance presents a common set of administrativesettings for each of the plurality of secure storage appliancesassociated with the virtual secure storage appliance, the common set ofadministrative settings remaining accessible to the administratordespite a failure of a respective secure storage appliance.

Operational flow proceeds to a heartbeat generation module 2204. Ingeneral, heartbeat generation module 2204 corresponds to thetransmission and reception of a operational status signal (heartbeatsignal) a primary secure storage appliance and a secondary securestorage appliance to determine if each respective secure storageappliance is functioning correctly. In one example embodiment, aphysical communication path is formed between the primary secure storageappliance and the secondary secure storage appliance to facilitate thetransmission and reception of the heartbeat signal, such as via a TCP/IPcommunication path. Other transmission methods are possible as well. Inthe example embodiment, from a perspective of the secondary securestorage appliance, upon successful transmission of a heartbeat statussignal to the primary secure storage appliance at heartbeat generationmodule 2204, operational flow proceeds to a heartbeat acknowledgmentmodule 2206.

In one aspect, heartbeat acknowledgment module 2206 corresponds toreception of an acknowledgement heartbeat signal from the primary securestorage appliance, indicating proper functional operation of the primarysecure storage appliance. Upon a positive reception of the heartbeatsignal at the secondary secure storage appliance, operational flowbranches “Yes” and proceeds to heartbeat generation module 2204.Operational flow continues between heartbeat generation module 2204 andheartbeat acknowledgment module 2206 until a negative determination ismade at heartbeat acknowledgment module 2206, indicating an absence of aheartbeat signal, and consequently a potential error in the operatingstatus of the primary secure storage appliance.

Upon a negative determination at heartbeat acknowledgment module 2206,operational flow branches “No” and proceeds to a failover evaluationmodule 2208. In one aspect, failover evaluation module 2208 proceeds todetermine if a potential block level I/O message can be executed by thesecondary secure storage appliance via an assessment of the status of aplurality of elements in the network. For example, the secondary securestorage appliance can determine if a requisite number of functioningfront-end network and back-end network secure data paths are availableto secondary secure storage appliance such than an I/O message can beexecuted, in accordance with conditions as described above withreference to FIGS. 19-21.

Upon a negative determination at failover evaluation module 2208operational flow branches “No” and proceeds to a backup failover attemptmodule 2220. In one aspect, execution of backup failover attempt module2220 corresponds to a transfer of an inquiry message from the secondarysecure storage appliance to an alternate secondary secure storageappliance. In one example embodiment, the alternate secondary securestorage appliance is identified via accessing a local copy of a networkconfiguration database in which a common set of administrative settings,such as primary and secondary secure storage appliance configurations,are defined on an individual volume basis. Upon a successfultransmission of the inquiry message from the secondary secure storageappliance to the alternate secondary secure storage appliance at backupfailover attempt module 2220, operational flow proceeds failoverevaluation module 2208. Operational flow continues between failoverevaluation module 2208 and backup failover attempt module 2220 until itis determined that a valid failover can occur.

Upon a positive determination at failover evaluation module 2208,indicating that a potential I/O message as presented by the client wouldbe executable, operational flow branches “Yes” and proceeds to afailover proceed module 2210. In one aspect, execution of failoverproceed module 2210 corresponds to a reassignment of the volume to thesecondary secure storage appliance such that the secondary securestorage appliance is rendered as the new primary secure storageappliance. Further the respective volume is disassociated from theprimary secure storage appliance. In certain embodiments, failoverproceed module 2210 further corresponds to the secondary secure storageappliance configuring one or more secure front-end network data paths tothe respective client and configuring one or more secure back-end datapaths to a one or more storage devices. Upon a successful execution offailover proceed module 2210, operational flow proceeds to an errormessage transfer module 2212, which transfers or forwards an errormessage to the administrator such that the I/O path failure and failovercan be addressed and/or investigated.

Upon successful transmission of the error message at error messagetransfer module 2212, operational flow proceeds to restore operationmodule 2214. In certain embodiments, restore operation module 2214corresponds to a restoration of operation of the failed secure storageappliance, and possible restoration of the failed secure storageappliance as the primary secure storage appliance for the respectivevolume. Operational flow proceeds to a copy database module 2216. Copydatabase module 2216 corresponds to a transfer of a copy of an updatedconfiguration database to the failed primary secure storage appliance asrestored at restore operation module 2214. In certain embodiments, copydatabase module 2216 is executed at the secondary secure storageappliance that assumed the role as the new primary secure storageappliance detects the restoration of the failed secure storage applianceat restore operation module 2214. Subsequently, the secondary securestorage appliance transfers a copy of the updated configuration databaseto the newly operational secure storage appliance. In other embodiments,the updated configuration database can be transferred to the newlyoperational secure storage appliance by an administrator device (e.g.,the administrator device 614 of FIGS. 12 and 19). Following a successfuloperation at copy database module 2216, indicating the restored securestorage appliance has obtained an updated configuration database,operational flow proceeds to end operation 2218, which corresponds totermination of the example systems and methods 2200.

Although FIGS. 19-22 present a few options regarding failover andfailover techniques for applications of the secure storage appliance andsecure network storage of data as described in the present disclosure,it is understood that further applications are possible as well.Furthermore, although each of these applications is described inconjunction with a particular network topology, it is understood that avariety of network topologies could be implemented to provide similarfunctionality, in a manner consistent with the principles describedherein.

It is recognized that the above networks, systems, and methods operateusing computer hardware and software in any of a variety ofconfigurations. Such configurations can include computing devices, whichgenerally include a processing device, one or more computer readablemedia, and a communication device. Other embodiments of a computingdevice are possible as well. For example, a computing device can includea user interface, an operating system, and one or more softwareapplications. Several example computing devices include a personalcomputer (PC), a laptop computer, or a personal digital assistant (PDA).A computing device can also include one or more servers, one or moremass storage databases, and/or other resources.

A processing device is a device that processes a set of instructions.Several examples of a processing device include a microprocessor, acentral processing unit, a microcontroller, a field programmable gatearray, and others. Further, processing devices may be of any generalvariety such as reduced instruction set computing devices, complexinstruction set computing devices, or specially designed processingdevices such as an application-specific integrated circuit device.

Computer readable media includes volatile memory and non-volatile memoryand can be implemented in any method or technology for the storage ofinformation such as computer readable instructions, data structures,program modules, or other data. In certain embodiments, computerreadable media is integrated as part of the processing device. In otherembodiments, computer readable media is separate from or in addition tothat of the processing device. Further, in general, computer readablemedia can be removable or non-removable. Several examples of computerreadable media include, RAM, ROM, EEPROM and other flash memorytechnologies, CD-ROM, digital versatile disks (DVD) or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or any other medium that can be used tostore desired information and that can be accessed by a computingdevice. In other embodiments, computer readable media can be configuredas a mass storage database that can be used to store a structuredcollection of data accessible by a computing device.

A communications device establishes a data connection that allows acomputing device to communicate with one or more other computing devicesvia any number of standard or specialized communication interfaces suchas, for example, a universal serial bus (USB), 802.11a/b/g network,radio frequency, infrared, serial, or any other data connection. Ingeneral, the communication between one or more computing devicesconfigured with one or more communication devices is accomplished via anetwork such as any of a number of wireless or hardwired WAN, LAN, SAN,Internet, or other packet-based or port-based communication networks.

The above specification, examples and data provide a completedescription of the manufacture and use of the composition of theinvention. Since many embodiments of the invention can be made withoutdeparting from the spirit and scope of the invention, the inventionresides in the claims hereinafter appended.

The invention claimed is:
 1. A method of maintaining data connectivityin a secure data storage network, the method comprising: assigning avolume to a primary secure storage appliance located in a secure datastorage network the primary secure storage appliance selected from amonga plurality of secure storage appliances located in the secure datastorage network, the volume presented as a virtual disk to a clientdevice and mapped to a physical storage at each of a plurality ofstorage systems; storing data, by the primary secure storage appliance,in the volume as blocks spread across the plurality of storage systems,the data stored across the plurality of storage systems arecryptographically split into a plurality of secondary data blocks thatare stored in separate volumes; detecting at one of the plurality ofsecure storage appliances a failure of the primary secure storageappliance; upon detecting the failure of the primary secure storageappliance, reassigning the volume to a second secure storage appliancefrom among the plurality of secure storage appliances, thereby renderingthe second secure storage appliance a new primary secure storageappliance; wherein in cryptographically splitting the data into theplurality of secondary data blocks utilizes a plurality of encryptionkeys to create a plurality of separate community of interest of datasets in which the data sets and corresponding plurality of secondarydata blocks are members of the community of interest associated with theone of the plurality of encryption keys used in the write requests. 2.The method of claim 1, wherein detecting the failure of the primarysecure storage appliance includes determining an absence of a heartbeatsignal transmitted periodically among the plurality of secure storageappliances.
 3. The method of claim 1, wherein the plurality of securestorage appliances are connected within a cluster.
 4. The method ofclaim 1, further comprising, upon reassigning the volume to a secondsecure storage appliance, sending an error message to an administratorof the secure data storage network.
 5. The method of claim 1, whereinthe primary secure storage appliance and the second secure storageappliance are each connected to the plurality of storage systems.
 6. Themethod of claim 1, further comprising presenting an administrativeinterface to an administrator of the secure data storage network, theadministrative interface presenting the plurality of secure storageappliances as a virtual secure storage appliance.
 7. The method of claim6, further comprising presenting a common set of administrative settingsfor each of the plurality of secure storage appliances associated withthe virtual secure storage appliance.
 8. The method of claim 7, whereinthe common set of administrative settings is stored at each of theplurality of secure storage appliances.
 9. The method of claim 1,further comprising restoring operation of the primary secure storageappliance.
 10. The method of claim 9, further comprising detectingrestoration operation of the primary secure storage appliance at one ofthe plurality of secure storage appliances.
 11. The method of claim 10,further comprising restoring a common set of administrative settings forthe plurality of secure storage appliances to the primary secure storageappliance.
 12. The method of claim 10, further comprising reassigningthe volume to the primary secure storage appliance and disassociatingthe second secure storage appliance from the volume.
 13. A secure datastorage network comprising: a client device; a plurality of storagesystems; a plurality of secure storage appliances interconnected betweenthe client device and the plurality of storage systems, the plurality ofsecure storage appliances including a primary secure storage applianceassociated with a volume, the volume presented as a virtual disk to theclient device and mapped to a physical storage at each of the pluralityof storage systems; wherein each of the plurality of secure storageappliances includes a common set of administrative information, and eachof the plurality of secure storage appliances monitors operationalstatus of one or more of a different secure storage appliance among theplurality of secure storage appliances; wherein data is stored in thevolume as blocks spread across the plurality of storage systems by theprimary secure storage appliance and the data stored in the volume beingcryptography split into a plurality of secondary data blocks that arestored in separate volumes of virtual disks; and the cryptographicallysplitting the data into the plurality of secondary data blocks utilizesa plurality of encryption keys to create a plurality of separatecommunity of interest of data sets in which the data sets andcorresponding plurality of secondary data blocks are members of thecommunity of interest associated with the one of the plurality ofencryption keys used in write requests.
 14. The secure data storagenetwork of claim 13, wherein each of the plurality of secure storageappliances is configured to periodically transmit a heartbeat message toanother secure storage appliance from among the plurality of securestorage appliances.
 15. The secure data storage network of claim 13,further comprising an administrative interface hosted by anadministrative console, the administrative interface providing a view ofa virtual secure storage appliance representing the plurality of securestorage appliances and presenting a common set of administrativesettings associated with the plurality of secure storage appliances. 16.The secure data storage network of claim 13, wherein the plurality ofsecure storage appliances reside within a cluster in the secure datastorage network.